Triple
T28068222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow derby |
E709314
|
entity |
| Predicate | isKeyFixtureIn |
P147838
|
FINISHED |
| Object | Scottish football calendar |
—
|
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 calendar | Statement: [Glasgow derby, isKeyFixtureIn, Scottish football calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyFixtureIn Context triple: [Glasgow derby, isKeyFixtureIn, Scottish football calendar]
-
A.
isMajorFixtureIn
chosen
Indicates that an entity plays a primary, prominent, or central role within a particular context, setting, or system.
-
B.
isInKey
Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured context.
-
C.
primaryFixture
Indicates that one entity serves as the main or principal fixture associated with another entity.
-
D.
isKeyPostIn
Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
-
E.
isKeySpineFor
Indicates that one entity serves as the central or foundational support structure upon which another entity critically depends.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 8:44 p.m.