Triple
T27047845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABBA – Waterloo |
E684689
|
entity |
| Predicate | resultInCompetition |
P8651
|
FINISHED |
| Object | winner |
—
|
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: winner | Statement: [ABBA – Waterloo, resultInCompetition, winner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultInCompetition Context triple: [ABBA – Waterloo, resultInCompetition, winner]
-
A.
competitionResult
chosen
Indicates the outcome of a competitive event, specifying how participants placed or performed relative to one another.
-
B.
resultOfParticipation
Indicates that something occurs or is produced as a consequence of an entity’s participation in an event or activity.
-
C.
statusInCompetition
Indicates the current standing or role an entity holds within a specific competition or contest.
-
D.
servedCompetition
Indicates that one entity provided service, participation, or representation in a competitive event or context involving another entity.
-
E.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 8:11 a.m.