Triple
T35928335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimní stadion Ivana Hlinky |
E1039084
|
entity |
| Predicate | hasFullOfficialName |
P184916
|
FINISHED |
| Object | Zimní stadion Ivana Hlinky |
—
|
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: Zimní stadion Ivana Hlinky | Statement: [Zimní stadion Ivana Hlinky, hasFullOfficialName, Zimní stadion Ivana Hlinky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFullOfficialName Context triple: [Zimní stadion Ivana Hlinky, hasFullOfficialName, Zimní stadion Ivana Hlinky]
-
A.
hasOfficialNameContaining
Indicates that an entity’s official name includes a specified substring or sequence of characters.
-
B.
hasOfficialNameStatus
Indicates that an entity’s official name is associated with a particular status or classification (e.g., current, former, provisional).
-
C.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
-
D.
hasOfficialDualNameWith
Indicates that two entities share an officially recognized dual or joint name used in formal contexts.
-
E.
hasOfficialShortNameInEnglish
Indicates that an entity has a designated official short form of its name expressed in English.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:07 p.m.