Triple
T24241689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria at the Eurovision Song Contest 1966 |
E603243
|
entity |
| Predicate | finalPosition |
P55492
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Austria at the Eurovision Song Contest 1966, finalPosition, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalPosition Context triple: [Austria at the Eurovision Song Contest 1966, finalPosition, 1]
-
A.
finishPosition
chosen
Indicates the final rank or place an entity achieves in an ordered outcome, such as a race, competition, or sequence of results.
-
B.
finalValue
Indicates the resulting or ultimate value obtained after all relevant operations, changes, or calculations have been completed.
-
C.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
D.
conclusionPosition
Indicates the position or location where a conclusion appears within a larger structure, sequence, or document.
-
E.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28aa04fe08190922d6abde695571a |
completed | April 29, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:03 a.m.