Triple
T31357316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bon Accord F.C. |
E799770
|
entity |
| Predicate | matchTypeOfRecordDefeat |
P155252
|
FINISHED |
| Object | cup tie |
—
|
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: cup tie | Statement: [Bon Accord F.C., matchTypeOfRecordDefeat, cup tie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchTypeOfRecordDefeat Context triple: [Bon Accord F.C., matchTypeOfRecordDefeat, cup tie]
-
A.
methodOfDefeat
Indicates the specific way or technique by which one entity defeats or overcomes another.
-
B.
defeatedInBoutType
chosen
Indicates that one entity lost to another in a competitive match of a specified bout type or ruleset.
-
C.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
D.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
E.
defeatSymbolizes
Indicates that an instance of defeat is used to symbolically represent or stand for another concept, state, or idea.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f48370481909e9d58d2cbff9466 |
completed | May 3, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.