Triple
T6996418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priene |
E162226
|
entity |
| Predicate | hasUrbanPlanType |
P54635
|
FINISHED |
| Object | Hippodamian plan |
—
|
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: Hippodamian plan | Statement: [Priene, hasUrbanPlanType, Hippodamian plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanPlanType Context triple: [Priene, hasUrbanPlanType, Hippodamian plan]
-
A.
hasUrbanPlanning
Indicates that an entity is involved in, responsible for, or characterized by activities or attributes related to urban planning.
-
B.
partOfUrbanPlanBy
Indicates that something is included as a component or element within an urban plan created or overseen by a specified agent.
-
C.
mainUrbanPlan
chosen
Indicates the primary urban planning scheme or framework that governs the development and organization of a given area.
-
D.
hasUrbanPlanner
Indicates that an entity is associated with or utilizes a specific urban planner responsible for planning or managing its urban development.
-
E.
hasUrbanClassification
Indicates that an entity is assigned a specific urban status or category within a defined classification system.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbedafa48190af0d2b47e3a1e17e |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.