Triple
T19540092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place des Pyramides |
E488873
|
entity |
| Predicate | districtFunction |
P51431
|
FINISHED |
| Object | commercial area |
—
|
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: commercial area | Statement: [Place des Pyramides, districtFunction, commercial area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: districtFunction Context triple: [Place des Pyramides, districtFunction, commercial area]
-
A.
district
Indicates that one entity is an administrative or electoral district that geographically contains or governs another entity.
-
B.
districtAdministration
Indicates that an entity is responsible for managing, governing, or overseeing the administrative affairs of a specific district or local jurisdiction.
-
C.
countyFunction
Indicates that a county serves a particular administrative or governmental role or performs a specified function.
-
D.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
E.
cityDistrictFunction
chosen
Indicates that a specific function, role, or land-use purpose is assigned to or characterizes a particular district within a city.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63871d00881909ed7371ae5577957 |
completed | April 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.