Triple
T581497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan de Fuca Ridge |
E15067
|
entity |
| Predicate | distanceFromCoast |
P15760
|
FINISHED |
| Object | approximately 300 to 500 kilometers offshore |
—
|
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 300 to 500 kilometers offshore | Statement: [Juan de Fuca Ridge, distanceFromCoast, approximately 300 to 500 kilometers offshore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCoast Context triple: [Juan de Fuca Ridge, distanceFromCoast, approximately 300 to 500 kilometers offshore]
-
A.
distanceToPacificOcean
Indicates the physical distance between a given location or entity and the Pacific Ocean.
-
B.
distanceFromMainland
Indicates the measured spatial separation between a location and the nearest point on the mainland.
-
C.
basedOnCoast
Indicates that something is situated along, adjacent to, or directly influenced by a coastline.
-
D.
distanceToContinentApproximate
Indicates an approximate measure of how far something is from a specified continent.
-
E.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b84899881909d5b2b4e67e22d9b |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985a2d08819090947895d9439e06 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.