Triple
T24199043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castell |
E599918
|
entity |
| Predicate | hasPostalAddressCountryCode |
P17984
|
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: [Castell, hasPostalAddressCountryCode, DE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalAddressCountryCode Context triple: [Castell, hasPostalAddressCountryCode, DE]
-
A.
hasPostalCountryCode
chosen
Indicates that an entity is associated with a specific country code used for postal addressing or mail routing.
-
B.
hasPostalAddressSystem
Indicates that an entity possesses or is served by an organized system for assigning and managing postal addresses.
-
C.
hasPostalAdministrationCountry
Indicates that a postal administration is under the jurisdiction of, or officially associated with, a particular country.
-
D.
hasPostalAddressComponent
Indicates that an entity is associated with a specific part or element of a postal address (such as street, city, or postal code).
-
E.
hasPostalSystemOf
Indicates that one entity possesses, uses, or is characterized by the postal system belonging to another 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9f61f881909f7e1287388ff982 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.