Triple
T9437431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbroath F.C. |
E227546
|
entity |
| Predicate | recordMatchScore |
P67862
|
FINISHED |
| Object | 36–0 |
—
|
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: 36–0 | Statement: [Arbroath F.C., recordMatchScore, 36–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordMatchScore Context triple: [Arbroath F.C., recordMatchScore, 36–0]
-
A.
matchRatio
Indicates the degree of similarity or correspondence between two items, typically expressed as a numerical ratio or percentage.
-
B.
scoringRecord
chosen
Indicates that there exists a record documenting a scoring event or outcome associated with the given entities.
-
C.
scoresWhen
Indicates that one entity achieves a score or points at the time or under the condition specified by another entity or event.
-
D.
scoredInMatch
Indicates that an entity (typically a player or team) scored during a particular match.
-
E.
coScoredWith
Indicates that two or more entities received the same score or were evaluated with an identical scoring outcome in a shared context.
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7edff5e881909b72976e8909ba4b |
completed | April 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:50 p.m.