Triple
T27521431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDS |
E694715
|
entity |
| Predicate | codeLettersMeaning |
P72708
|
FINISHED |
| Object | Landkreis Dahme-Spreewald |
—
|
NE NERFINISHED |
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: Landkreis Dahme-Spreewald | Statement: [LDS, codeLettersMeaning, Landkreis Dahme-Spreewald]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeLettersMeaning Context triple: [LDS, codeLettersMeaning, Landkreis Dahme-Spreewald]
-
A.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
-
B.
lettersMeaning
chosen
Indicates that a set of letters or characters represents, signifies, or conveys a particular meaning or message.
-
C.
digitMeaning
Indicates that a particular digit symbol is associated with a specific numerical value or conceptual meaning.
-
D.
codeNameMeaning
Indicates that one entity is the meaning, interpretation, or significance associated with another entity’s code name.
-
E.
associatedCharacterMeaning
Indicates that there is a relationship between a character and the meaning, interpretation, or concept that this character is intended to represent.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f2ba2b88190962819631042d02d |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:21 p.m.