Triple
T35986710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hennenman |
E1040729
|
entity |
| Predicate | provinceIsoCode |
P197431
|
FINISHED |
| Object | ZA-FS |
—
|
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: ZA-FS | Statement: [Hennenman, provinceIsoCode, ZA-FS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceIsoCode Context triple: [Hennenman, provinceIsoCode, ZA-FS]
-
A.
provinceISOCode
chosen
Indicates the standardized ISO code assigned to the province associated with the subject entity.
-
B.
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.
-
C.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
D.
postalCountry
Indicates the country associated with an entity’s postal or mailing address.
-
E.
countryDeJure
Indicates that one entity is the legally recognized (de jure) country having sovereignty or authority over 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: May 3, 2026, 4:07 p.m.