Triple
T9437432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbroath F.C. |
E227546
|
entity |
| Predicate | recordMatchDate |
P61567
|
FINISHED |
| Object | 12 September 1885 |
—
|
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: 12 September 1885 | Statement: [Arbroath F.C., recordMatchDate, 12 September 1885]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordMatchDate Context triple: [Arbroath F.C., recordMatchDate, 12 September 1885]
-
A.
recordGameDate
chosen
Indicates that an entity logs or stores the date on which a particular game took place or is scheduled.
-
B.
finalMatchDate
Indicates the calendar date on which the final or deciding match in a series, tournament, or competition takes place.
-
C.
firstMLSMatchDate
Indicates the calendar date on which an entity (typically a player or team) participated in its first official Major League Soccer (MLS) match.
-
D.
firstOfficialMatchDate
Indicates the date on which an entity’s first official match or game was played.
-
E.
dateOfRecordKnockout
Indicates the date on which a particular record was invalidated, removed, or otherwise rendered no longer in effect.
- 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.