Triple
T21293197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aarburg |
E524848
|
entity |
| Predicate | isoLanguageCode |
P5196
|
FINISHED |
| Object | de |
—
|
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 | Statement: [Aarburg, isoLanguageCode, de]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isoLanguageCode Context triple: [Aarburg, isoLanguageCode, de]
-
A.
isoLanguageOf
Indicates that one entity is the ISO 639 language code corresponding to the language represented by the other entity.
-
B.
languageCodeISO639-2
Indicates that an entity is associated with a language identified by its ISO 639-2 three-letter code.
-
C.
languageCodeISO639-1
chosen
Indicates that the subject entity is associated with the specified two-letter ISO 639-1 language code.
-
D.
ISO639Language
Indicates that an entity is associated with a language identified or classified according to the ISO 639 language code standard.
-
E.
ISO639-3CodeOfLanguage
Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73856ba988190a8359efecea362cc |
completed | April 21, 2026, 8:41 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:04 p.m.