Triple
T25283436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surapadman |
E633874
|
entity |
| Predicate | emblemOfAfterDefeat |
P86429
|
FINISHED |
| Object | Murugan's rooster emblem |
—
|
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: Murugan's rooster emblem | Statement: [Surapadman, emblemOfAfterDefeat, Murugan's rooster emblem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemOfAfterDefeat Context triple: [Surapadman, emblemOfAfterDefeat, Murugan's rooster emblem]
-
A.
afterDefeat
chosen
Indicates that one event, state, or action occurs subsequent to and as a consequence of a defeat of some party or entity.
-
B.
finalDefeatIn
Indicates that one entity experiences its ultimate or conclusive defeat within a specified event, context, or location.
-
C.
defeatSymbolizes
Indicates that an instance of defeat is used to symbolically represent or stand for another concept, state, or idea.
-
D.
significantDefeat
Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
-
E.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0718908190a2ebc862db79e2ea |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:19 p.m.