Triple
T36940652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Großwardein |
E913752
|
entity |
| Predicate | hasAlternativeNameInRomanian |
P23117
|
FINISHED |
| Object | Oradea |
—
|
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: Oradea | Statement: [Großwardein, hasAlternativeNameInRomanian, Oradea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeNameInRomanian Context triple: [Großwardein, hasAlternativeNameInRomanian, Oradea]
-
A.
nameInRomanian
chosen
Indicates that one entity is the Romanian-language name or designation of another entity.
-
B.
hasAlternativeNameOfParentLanguage
Indicates that an entity has an alternative or variant name derived from or associated with the name of its parent language.
-
C.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
D.
hasAlternativeToponymy
Indicates that an entity is associated with one or more alternative place names or toponyms used to refer to the same geographic location.
-
E.
hasEnglishNameVariant
Indicates that one entity is an alternative or variant form of another entity’s name specifically in the English language.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 4:13 p.m.