Triple
T9233615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place des États-Unis |
E221881
|
entity |
| Predicate | cityQuarterFunction |
P51431
|
FINISHED |
| Object | representative square |
—
|
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: representative square | Statement: [Place des États-Unis, cityQuarterFunction, representative square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityQuarterFunction Context triple: [Place des États-Unis, cityQuarterFunction, representative square]
-
A.
situatedInQuarter
Indicates that one entity is located within or belongs to a specific quarter or district of a larger area.
-
B.
cityDistrictFunction
chosen
Indicates that a specific function, role, or land-use purpose is assigned to or characterizes a particular district within a city.
-
C.
cityDistrictLevel
Indicates that one administrative unit is a district-level subdivision within a given city in the territorial hierarchy.
-
D.
cityDistrictType
Indicates the type or classification of a city district within an urban or administrative structure.
-
E.
hasCityQuarterStatus
Indicates that an entity holds the official status or designation of being a city quarter within a larger urban area.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee1baa3c8190870d1e850ccab1e0 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:29 p.m.