Triple
T28558087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch ABC islands |
E723058
|
entity |
| Predicate | BonaireStatus |
P33447
|
FINISHED |
| Object | special municipality of the Netherlands |
—
|
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: special municipality of the Netherlands | Statement: [Dutch ABC islands, BonaireStatus, special municipality of the Netherlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BonaireStatus Context triple: [Dutch ABC islands, BonaireStatus, special municipality of the Netherlands]
-
A.
statusInSintMaarten
Indicates the legal, social, or official standing or condition that an entity has within the jurisdiction of Sint Maarten.
-
B.
statusInDominica
Indicates that an entity holds a particular legal, social, or official status within the jurisdiction of Dominica.
-
C.
countrySpecificStatus
chosen
Indicates a status or condition that is defined or applied specifically in the context of a particular country.
-
D.
statusInSuriname
Indicates the legal, social, or official standing or condition that an entity holds within the context of Suriname.
-
E.
landerStatus
Indicates the current operational or situational state of a lander in its mission lifecycle.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6505193988190b1e7879009d997ef |
completed | May 2, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:47 a.m.