Triple
T20253484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iffland-Ring |
E498619
|
entity |
| Predicate | mainUsageLanguage |
P18209
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Iffland-Ring, mainUsageLanguage, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainUsageLanguage Context triple: [Iffland-Ring, mainUsageLanguage, German]
-
A.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
B.
usesLanguageAs
Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
-
C.
languageUse
chosen
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
D.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
E.
primaryLanguageType
Indicates the main category or kind of language (such as spoken, written, or signed) that serves as the primary mode of communication in a given context or for a given 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673aa42348190852ae8313f4494ca |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.