Triple
T34270614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emericus |
E879303
|
entity |
| Predicate | hasOriginLanguageOfBaseName |
P1754
|
FINISHED |
| Object | Hungarian |
—
|
LITERAL FINISHED |
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: Hungarian | Statement: [Emericus, hasOriginLanguageOfBaseName, Hungarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginLanguageOfBaseName Context triple: [Emericus, hasOriginLanguageOfBaseName, Hungarian]
-
A.
hasLanguageOfOrigin
chosen
Indicates that one entity has its origin or source in the language specified by another entity.
-
B.
hasTranslationBase
Indicates that one entity serves as the original source or base text from which the other entity is translated.
-
C.
hasAlternativeNameOfParentLanguage
Indicates that an entity has an alternative or variant name derived from or associated with the name of its parent language.
-
D.
hasEndonymLanguage
Indicates that the language specified is the one in which a name or term is expressed in its own native or local form.
-
E.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: May 1, 2026, 1:56 a.m.