Triple
T7530626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chain of Craters Road |
E178012
|
entity |
| Predicate | terminusFeature |
P77353
|
FINISHED |
| Object | lava-covered sections from past eruptions |
—
|
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: lava-covered sections from past eruptions | Statement: [Chain of Craters Road, terminusFeature, lava-covered sections from past eruptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusFeature Context triple: [Chain of Craters Road, terminusFeature, lava-covered sections from past eruptions]
-
A.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
B.
terminusType
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
C.
terminusJunction
Indicates a relationship where a route, line, or path ends at a junction point that serves as its terminal connection.
-
D.
terminusRegion
Indicates the region or area where something (such as a route, line, or process) ends or reaches its final point.
-
E.
terminusUpper
Indicates that one entity serves as the upper or final endpoint (terminus) of another entity, such as a route, segment, or ordered structure.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8217b1c8190b3db453cee0fc4fd |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f555455c81908850210bcad96ac2 |
completed | March 27, 2026, 9:23 p.m. |
Created at: March 27, 2026, 3:47 p.m.