Triple
T137723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunfermline Athletic F.C. |
E2783
|
entity |
| Predicate | typeOfClub |
P3580
|
FINISHED |
| Object | Scottish football club |
—
|
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: Scottish football club | Statement: [Dunfermline Athletic F.C., typeOfClub, Scottish football club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfClub Context triple: [Dunfermline Athletic F.C., typeOfClub, Scottish football club]
-
A.
typeOfTeams
Indicates the categories or kinds of teams to which an entity or group of entities belongs.
-
B.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
C.
organizationType
chosen
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
-
D.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
E.
sportsFacility
Indicates that one entity is a sports facility where sports or physical activities can take place for the other entity.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a6cab88190944c8f74d8d1605c |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25652efdc8190b85b33735a9e6370 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.