Triple
T36941418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Kings Islands |
E913777
|
entity |
| Predicate | hasHighestPoint_m |
P200160
|
FINISHED |
| Object | 295 |
—
|
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: 295 | Statement: [Three Kings Islands, hasHighestPoint_m, 295]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestPoint_m Context triple: [Three Kings Islands, hasHighestPoint_m, 295]
-
A.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
-
B.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
-
D.
hasHighestElevationsOf
Indicates that one entity possesses the greatest elevation values (e.g., altitudes or heights) compared to another entity or set of entities.
-
E.
highestPointFeature
Indicates that one entity is the feature or element that constitutes the highest point of another entity (such as a place, structure, or area).
- F. None of above. chosen
Provenance (4 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69ff779d3d788190af5a2dbc4d7ca3c8 |
completed | May 9, 2026, 6:06 p.m. |
Created at: May 3, 2026, 4:13 p.m.