Triple
T23331346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post Office House |
E591451
|
entity |
| Predicate | clockFamousFor |
P37670
|
FINISHED |
| Object | New Year’s Eve countdown in Spain |
—
|
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: New Year’s Eve countdown in Spain | Statement: [Post Office House, clockFamousFor, New Year’s Eve countdown in Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clockFamousFor Context triple: [Post Office House, clockFamousFor, New Year’s Eve countdown in Spain]
-
A.
inscriptionFamousFor
Indicates that an inscription is widely recognized or notable specifically because of the referenced feature, event, content, or characteristic.
-
B.
primaryCityLandmarkOf
Indicates that a landmark is a principal or defining landmark associated with a specific city.
-
C.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
D.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
-
E.
iconicFeature
chosen
Indicates that something serves as a distinctive, widely recognized characteristic or symbol of another entity.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197edfbbc81908cb56507cd280737 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:15 p.m.