Triple
T29759578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Sheridan |
E753724
|
entity |
| Predicate | distanceToAlert |
P202746
|
FINISHED |
| Object | approximately 13 km east |
—
|
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 13 km east | Statement: [Cape Sheridan, distanceToAlert, approximately 13 km east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAlert Context triple: [Cape Sheridan, distanceToAlert, approximately 13 km east]
-
A.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
distanceFromNosyBe
Indicates the spatial distance between a given entity or location and Nosy Be.
-
C.
distanceFromReading
Indicates the measured spatial distance between a specified entity and the location of Reading.
-
D.
distanceFromHypocenter
Indicates the measured distance between a specified location and the hypocenter (origin point) of an event such as an earthquake.
-
E.
distanceFromStation
Indicates the measured spatial separation between an entity and a specified station.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a00b3d2e0c88190a8bf49576e654f64 |
completed | May 10, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_6a00b376f4e48190a6676779fe02ea9f |
completed | May 10, 2026, 4:33 p.m. |
| PDg | Predicate description generation | batch_6a00b3d23bdc8190b45dd7eefa72ead5 |
completed | May 10, 2026, 4:35 p.m. |
Created at: April 28, 2026, 8:31 p.m.