Triple
T25126551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modri |
E629408
|
entity |
| Predicate | notableCompetitionContext |
P90573
|
FINISHED |
| Object | Prva HNL |
—
|
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: Prva HNL | Statement: [Modri, notableCompetitionContext, Prva HNL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCompetitionContext Context triple: [Modri, notableCompetitionContext, Prva HNL]
-
A.
competitionInNotableEvent
Indicates that an entity participated as a competitor in a specific notable event or competition.
-
B.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
-
C.
notableTournament
Indicates that an entity is a tournament of particular significance or prominence in relation to another entity.
-
D.
notableSportIncluded
Indicates that a particular sport is prominently featured or included as a notable component within something, such as an event, program, or context.
-
E.
hasCompetitionContext
chosen
Indicates that an entity is associated with or occurs within a specific competitive setting, event, or environment.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 18, 2026, 6:28 a.m.