Triple
T24953945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anzac Medal |
E624415
|
entity |
| Predicate | matchParticipants |
P15194
|
FINISHED |
| Object | Collingwood Football Club |
—
|
NE NERFINISHED |
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: Collingwood Football Club | Statement: [Anzac Medal, matchParticipants, Collingwood Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchParticipants Context triple: [Anzac Medal, matchParticipants, Collingwood Football Club]
-
A.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
B.
teamsParticipated
Indicates that the referenced teams took part in a particular event, activity, or competition.
-
C.
leagueParticipations
Indicates participation relationships where an entity takes part in one or more leagues or league seasons.
-
D.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
E.
teamParticipated
chosen
Indicates that a team took part in or was involved in a particular event, activity, or competition.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490283c481908c18246dc7125eec |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:57 a.m.