Triple
T34905996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DE-ST |
E1006726
|
entity |
| Predicate | hasLanguageIndependentForm |
P187568
|
FINISHED |
| Object | DE-ST |
—
|
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: DE-ST | Statement: [DE-ST, hasLanguageIndependentForm, DE-ST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageIndependentForm Context triple: [DE-ST, hasLanguageIndependentForm, DE-ST]
-
A.
hasLanguageNeutralForm
chosen
Indicates that an entity has a form or representation that is independent of any specific natural language.
-
B.
hasLanguageIndependentName
Indicates that an entity possesses a name or label that is the same across all languages, not tied to any specific linguistic form.
-
C.
isLanguageIndependent
Indicates that the relationship, property, or behavior holds true regardless of the specific natural language used to express or encode it.
-
D.
hasLanguageFormOf
Indicates that one entity is a specific linguistic form, expression, or realization of the language used by another entity.
-
E.
hasLanguageRepresentation
Indicates that an entity is expressed, encoded, or represented using a particular natural or formal 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: May 3, 2026, 4 p.m.