Triple
T28184896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond face routes |
E716149
|
entity |
| Predicate | typicalApproachVia |
P77723
|
FINISHED |
| Object | Chasm Lake |
—
|
NE NERFINISHED |
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: Chasm Lake | Statement: [Diamond face routes, typicalApproachVia, Chasm Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalApproachVia Context triple: [Diamond face routes, typicalApproachVia, Chasm Lake]
-
A.
standardApproach
chosen
Indicates that an entity uses or follows a commonly accepted, conventional, or typical method for addressing a task or problem.
-
B.
guardedApproachTo
Indicates a cautious, defensive, or wary manner of moving toward or engaging with another entity.
-
C.
usedToApproach
Indicates that one entity employed another entity as a means or method to move closer to or reach a target entity or location.
-
D.
controlledApproachTo
Indicates a deliberate, regulated, or carefully managed way of proceeding toward or dealing with another entity.
-
E.
approche
Indicates that one entity moves or positions itself closer to another entity or reference point.
- F. None of above.
Provenance (3 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: April 27, 2026, 10:22 p.m.