Triple
T3868319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colgate Clock |
E91914
|
entity |
| Predicate | elevationAboveWater |
P51570
|
FINISHED |
| Object | approximately 30 feet |
—
|
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: approximately 30 feet | Statement: [Colgate Clock, elevationAboveWater, approximately 30 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationAboveWater Context triple: [Colgate Clock, elevationAboveWater, approximately 30 feet]
-
A.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
B.
elevationAboveLake
Indicates the vertical height or altitude of something relative to the surface level of a specified lake.
-
C.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
D.
riverMouthElevation
Indicates the elevation at which a river reaches its mouth or endpoint, typically where it flows into another body of water.
-
E.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3dfb3c8190a0a07070f0d76bf6 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:19 p.m.