Triple
T24055878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Csíkszereda |
E595801
|
entity |
| Predicate | isHungarianExonymFor |
P27628
|
FINISHED |
| Object | Miercurea Ciuc |
—
|
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: Miercurea Ciuc | Statement: [Csíkszereda, isHungarianExonymFor, Miercurea Ciuc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHungarianExonymFor Context triple: [Csíkszereda, isHungarianExonymFor, Miercurea Ciuc]
-
A.
hasExonym
Indicates that one entity is known by an alternative name or designation in another language or cultural context.
-
B.
countryDuringKingdomOfHungary
Indicates that a country existed within the territorial or political bounds of the Kingdom of Hungary during a specified historical period.
-
C.
nameInHungarian
chosen
Indicates that one entity is the Hungarian-language name or designation of another entity.
-
D.
hasGivenNameFormInHungarian
Indicates that an entity’s given name is expressed in its specific Hungarian linguistic form.
-
E.
countryDuringAustriaHungaryPeriod
Indicates that an entity functioned as a country or territorial unit during the historical period when Austria-Hungary existed.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9d65e608190b22a81ae4f94daff |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:30 p.m.