Triple
T10378065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAVD 88 |
E244556
|
entity |
| Predicate | referenceTideGaugeType |
P93671
|
FINISHED |
| Object | primary tidal benchmark |
—
|
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: primary tidal benchmark | Statement: [NAVD 88, referenceTideGaugeType, primary tidal benchmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceTideGaugeType Context triple: [NAVD 88, referenceTideGaugeType, primary tidal benchmark]
-
A.
tideType
Indicates the specific category or phase of the tide (such as high, low, rising, or falling) associated with a given tidal event or condition.
-
B.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
C.
tidalCurrentCharacteristic
Indicates the specific properties or behavior of a tidal current, such as its strength, direction, or variability.
-
D.
tsunamiType
Indicates the specific classification or category of a tsunami associated with an event or location.
-
E.
oceanographicType
Indicates the specific oceanographic classification or category associated with an entity, such as a type of ocean feature, condition, or measurement.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98f312481909f7276fc3762d7bc |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:03 p.m.