Triple
T31357309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bon Accord F.C. |
E799770
|
entity |
| Predicate | roleInRecordMatch |
P200862
|
FINISHED |
| Object | losing team in Arbroath 36–0 Bon Accord |
—
|
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: losing team in Arbroath 36–0 Bon Accord | Statement: [Bon Accord F.C., roleInRecordMatch, losing team in Arbroath 36–0 Bon Accord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRecordMatch Context triple: [Bon Accord F.C., roleInRecordMatch, losing team in Arbroath 36–0 Bon Accord]
-
A.
roleAtMatches
Indicates that an entity’s role or position at a given time or context matches a specified role criterion.
-
B.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
C.
roleInMetadata
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
D.
roleAtYepRocRecords
Indicates the specific role or position an entity holds at Yep Roc Records.
-
E.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
- F. None of above. chosen
Provenance (4 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_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
| PDg | Predicate description generation | batch_69ffb5c2cef0819087a92a1a5ab694a8 |
completed | May 9, 2026, 10:31 p.m. |
Created at: April 29, 2026, 9:17 p.m.