Triple
T3021811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weingarten (Lichtenfels) |
E82476
|
entity |
| Predicate | hasISO3166-1Code |
P189
|
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: [Weingarten (Lichtenfels), hasISO3166-1Code, DE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISO3166-1Code Context triple: [Weingarten (Lichtenfels), hasISO3166-1Code, DE]
-
A.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
-
B.
hasISOCode
chosen
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
-
C.
sharesISO3166CodeWith
Indicates that two entities are associated with and use the same ISO 3166 country code.
-
D.
parentISO3166Code
Indicates that one geographic or political entity is hierarchically contained within or derived from another, as represented by its parent ISO 3166 country or region code.
-
E.
hasISO3166Alpha3Code
Indicates that an entity is associated with a specific three-letter country code defined by the ISO 3166-1 alpha-3 standard.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a963034819093d96566e9b0cea9 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.