Triple
T15473523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tricity Derby |
E376724
|
entity |
| Predicate | primaryFixture |
P118387
|
FINISHED |
| Object | Lechia Gdańsk vs Arka Gdynia |
—
|
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: Lechia Gdańsk vs Arka Gdynia | Statement: [Tricity Derby, primaryFixture, Lechia Gdańsk vs Arka Gdynia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFixture Context triple: [Tricity Derby, primaryFixture, Lechia Gdańsk vs Arka Gdynia]
-
A.
primaryMount
Indicates that one entity serves as the main or default mount (attachment or support point) for another entity.
-
B.
primaryAssembly
Indicates that one entity serves as the main or principal assembly to which another entity is structurally or organizationally related.
-
C.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
D.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
-
E.
primaryEquipment
Indicates that one entity serves as the main or most important piece of equipment used by another entity.
- F. None of above. chosen
Provenance (4 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6c57308190b4cfe661c26addd4 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:33 a.m.