Triple
T5909784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vroegnieuwnederlands |
E131429
|
entity |
| Predicate | taalcode |
P66880
|
FINISHED |
| Object | historische variëteit zonder moderne ISO-code |
—
|
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: historische variëteit zonder moderne ISO-code | Statement: [Vroegnieuwnederlands, taalcode, historische variëteit zonder moderne ISO-code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taalcode Context triple: [Vroegnieuwnederlands, taalcode, historische variëteit zonder moderne ISO-code]
-
A.
ISO639-3CodeOfLanguage
Indicates that one entity is the ISO 639-3 three-letter language code assigned 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
Indicates that the subject entity is associated with the specified two-letter ISO 639-1 language code.
-
D.
languageOfCode
Indicates that a programming code artifact is written in, or uses, a particular programming language.
-
E.
targetLanguage
Indicates the language that is the intended recipient or focus of a communication, translation, or linguistic operation.
- F. None of above. chosen
Provenance (4 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03edf98b881908e9dbc03d3fd6218 |
completed | March 22, 2026, 7:11 p.m. |
Created at: March 22, 2026, 3:59 p.m.