Triple
T25393215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HŠK Građanski |
E636222
|
entity |
| Predicate | regardedAsPredecessorOf |
P97
|
FINISHED |
| Object | GNK Dinamo Zagreb |
—
|
NE NERFINISHED |
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: GNK Dinamo Zagreb | Statement: [HŠK Građanski, regardedAsPredecessorOf, GNK Dinamo Zagreb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardedAsPredecessorOf Context triple: [HŠK Građanski, regardedAsPredecessorOf, GNK Dinamo Zagreb]
-
A.
contributedToPredecessorOf
Indicates that one entity contributed to or influenced another entity that came before a specified successor in a sequence or lineage.
-
B.
ownedByPredecessor
Indicates that something is or was owned by an entity that previously held a given role, position, or status before the current one.
-
C.
hasPredecessorRoleIn
Indicates that one role functioned earlier in time or sequence relative to another role within the same context or position.
-
D.
predecessorRelationship
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
-
E.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f56572b9288190abaf921c761fd843 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:49 p.m.