Triple
T28107072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian-Slovak |
E710392
|
entity |
| Predicate | mayInvolveLanguage |
P94296
|
FINISHED |
| Object | Hungarian language |
—
|
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: Hungarian language | Statement: [Hungarian-Slovak, mayInvolveLanguage, Hungarian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayInvolveLanguage Context triple: [Hungarian-Slovak, mayInvolveLanguage, Hungarian language]
-
A.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
B.
possibleLanguage
chosen
Indicates that an entity could plausibly be expressed, interpreted, or communicated in a given language.
-
C.
includesLanguage
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
-
D.
eligibleLanguage
Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
-
E.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 9:09 p.m.