Triple
T26953454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Gigantes–Teno cliffs |
E678834
|
entity |
| Predicate | hasMinimumHeight |
P84417
|
FINISHED |
| Object | about 300 metres |
—
|
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 300 metres | Statement: [Los Gigantes–Teno cliffs, hasMinimumHeight, about 300 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinimumHeight Context triple: [Los Gigantes–Teno cliffs, hasMinimumHeight, about 300 metres]
-
A.
hasMinimumSize
Indicates that an entity meets or exceeds a specified minimum size threshold.
-
B.
hasMinimum
chosen
Indicates that an entity possesses at least a specified lower bound or smallest allowable value, quantity, or level in relation to another entity or constraint.
-
C.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
D.
hasMinimumWeight
Indicates that an entity’s weight meets or exceeds a specified minimum threshold.
-
E.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 6:25 a.m.