Triple
T3482971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troyes |
E73536
|
entity |
| Predicate | hasHistoricCenterShape |
P49037
|
FINISHED |
| Object | champagne cork |
—
|
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: champagne cork | Statement: [Troyes, hasHistoricCenterShape, champagne cork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCenterShape Context triple: [Troyes, hasHistoricCenterShape, champagne cork]
-
A.
isInHistoricCenterOf
Indicates that one entity is located within the historic center area of another entity (typically a city or town).
-
B.
isHistoricCenterOf
Indicates that a place serves as the historically significant core or original central area of another location, typically a city or town.
-
C.
hasRebuiltHistoricCenter
Indicates that an entity has undertaken and completed the restoration or reconstruction of a historic city or town center.
-
D.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
-
E.
hasMajorHistoricalCentersIn
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
- F. None of above. chosen
Provenance (4 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb781e9c8190810fdd814f506127 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:17 p.m.