Triple
T7773235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benbecula |
E179123
|
entity |
| Predicate | hasLowPoint |
P35776
|
FINISHED |
| Object | sea level |
—
|
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: sea level | Statement: [Benbecula, hasLowPoint, sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowPoint Context triple: [Benbecula, hasLowPoint, sea level]
-
A.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
-
B.
hasLow
Indicates that an entity possesses a value, level, or amount of something that is below a defined or expected threshold.
-
C.
elevationLowerThan
Indicates that the elevation of one entity is lower than the elevation of another entity.
-
D.
hasLowestTerminusAmong
Indicates that one entity’s terminus (end point) is lower in position or elevation than the termini of all other compared entities.
-
E.
elevationMinApprox
chosen
Indicates an approximate value for the minimum elevation associated with an entity or location.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c70461b3e48190bf1e4d4f9e6bb08e |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:11 p.m.