Triple
T31446821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunas de Baní |
E802213
|
entity |
| Predicate | hasApproximateMaximumHeight |
P131486
|
FINISHED |
| Object | about 35 meters |
—
|
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: about 35 meters | Statement: [Dunas de Baní, hasApproximateMaximumHeight, about 35 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateMaximumHeight Context triple: [Dunas de Baní, hasApproximateMaximumHeight, about 35 meters]
-
A.
approximateMaximumHeight
chosen
Indicates the estimated upper limit of an entity’s height, rather than an exact measured value.
-
B.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
C.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
-
D.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
E.
hasMaximumStructureHeightRegulation
Indicates that there is a regulatory limit specifying the maximum allowable height for a structure.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 30, 2026, 9:10 p.m.