Triple
T794541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pars |
E16988
|
entity |
| Predicate | abbreviationOfName |
P3776
|
FINISHED |
| Object | colloquial form of Dunfermline Athletic |
—
|
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: colloquial form of Dunfermline Athletic | Statement: [The Pars, abbreviationOfName, colloquial form of Dunfermline Athletic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationOfName Context triple: [The Pars, abbreviationOfName, colloquial form of Dunfermline Athletic]
-
A.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
B.
abbreviation
Indicates that one term is a shortened or contracted form that stands for another, longer expression.
-
C.
abbreviationOfTeam
chosen
Indicates that one term is an abbreviation or shortened form of a team’s full name.
-
D.
establishesAbbreviation
Indicates that one entity defines or introduces an abbreviated form that stands for another entity.
-
E.
abbreviationOfAdministrator
Indicates that one term is an abbreviation for the title or role of an administrator.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79b976c819085cd381bbd597ca5 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.