Triple

T9193540
Position Surface form Disambiguated ID Type / Status
Subject cardo maximus of Leptis Magna E220646 entity
Predicate hasFunctionInPlan P46513 FINISHED
Object organizing city blocks and insulae — LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: organizing city blocks and insulae | Statement: [cardo maximus of Leptis Magna, hasFunctionInPlan, organizing city blocks and insulae]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFunctionInPlan
Context triple: [cardo maximus of Leptis Magna, hasFunctionInPlan, organizing city blocks and insulae]
  • A. hasPlanningFunction chosen
    Indicates that an entity is responsible for or involved in planning, organizing, or determining future actions or strategies.
  • B. hasFunctionInPresent
    Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
  • C. hasFunctionInComplex
    Indicates that an entity performs a specific functional role within a larger molecular or structural complex.
  • D. hasFunctionInPlot
    Indicates that an entity serves a particular role or purpose within the structure or progression of a plot.
  • E. containsFunction
    Indicates that one entity includes, defines, or provides the implementation of a particular function.
  • F. None of above.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69ca83e7ba70819088b74866d9da2c30 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd5c1fa9c8190bc5cc6dce8778694 completed April 1, 2026, 8:22 a.m.
PD Predicate disambiguation batch_69cc660af2408190ae06eb8326e1c64e completed April 1, 2026, 12:25 a.m.
Created at: March 30, 2026, 7:25 p.m.