Triple
T1072597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quai d'Orsay |
E23362
|
entity |
| Predicate | urbanPlanningRole |
P14108
|
FINISHED |
| Object | axis between Invalides and the Seine |
—
|
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: axis between Invalides and the Seine | Statement: [Quai d'Orsay, urbanPlanningRole, axis between Invalides and the Seine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanPlanningRole Context triple: [Quai d'Orsay, urbanPlanningRole, axis between Invalides and the Seine]
-
A.
roleInUrbanPlan
chosen
Indicates the specific function, responsibility, or position an entity holds within an urban planning context or scheme.
-
B.
urbanRole
Indicates the function, status, or role that an entity holds within an urban or city context.
-
C.
urbanPlanningStyle
Indicates the characteristic approach or methodology used in planning and organizing urban spaces and development.
-
D.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
E.
urbanDesign
Indicates the relationship in which an entity is responsible for planning, organizing, or shaping the physical layout and functional structure of urban spaces.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b9296c5c8190a3060fbfdf24f029 |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73844708190a16c9e9824ca2fb6 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.