Triple
T28491074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portugal at the Eurovision Song Contest 1996 |
E720965
|
entity |
| Predicate | performanceOrder |
P37518
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Portugal at the Eurovision Song Contest 1996, performanceOrder, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceOrder Context triple: [Portugal at the Eurovision Song Contest 1996, performanceOrder, 15]
-
A.
orderOf
chosen
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
B.
performanceAs
Indicates that one entity serves in a particular role, character, or capacity within a performance or presentation involving another entity.
-
C.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
D.
displayOrder
Indicates the sequence or position in which items should be presented or shown relative to one another.
-
E.
featuresOrder
Indicates that one entity specifies or determines the sequence or arrangement in which another entity’s features appear or are organized.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 28, 2026, 3:01 a.m.