Triple
T34768033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Chute |
E1002272
|
entity |
| Predicate | notablePlaceInText |
P205547
|
FINISHED |
| Object | Mexico City bar in Amsterdam |
—
|
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: Mexico City bar in Amsterdam | Statement: [La Chute, notablePlaceInText, Mexico City bar in Amsterdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlaceInText Context triple: [La Chute, notablePlaceInText, Mexico City bar in Amsterdam]
-
A.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
B.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
C.
notableText
Indicates that a particular piece of text is especially significant, prominent, or worthy of attention in relation to the associated entity or context.
-
D.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
E.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 3:59 p.m.