Triple
T27521430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDS |
E694715
|
entity |
| Predicate | languageOfCodeLetters |
P193406
|
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: [LDS, languageOfCodeLetters, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCodeLetters Context triple: [LDS, languageOfCodeLetters, German]
-
A.
languageOfCodes
Indicates that a particular language is used for or associated with a given set of codes.
-
B.
languageOfLetters
Indicates that one entity is the language in which the other entity’s letters or written correspondence are composed.
-
C.
languageOfCode
Indicates that a programming code artifact is written in, or uses, a particular programming language.
-
D.
alphabeticCode
Indicates that one entity is identified or represented by a specific alphabetic code assigned to it.
-
E.
hasCodeLetters
Indicates that an entity is associated with, or represented by, a specific sequence of letters used as its code or identifier.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
| PDg | Predicate description generation | batch_69fd474a71648190b6b6ae4991db81b1 |
completed | May 8, 2026, 2:15 a.m. |
Created at: April 27, 2026, 1:21 p.m.