Triple
T4047251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Couloir |
E84095
|
entity |
| Predicate | bestCrossed |
P53796
|
FINISHED |
| Object | early morning |
—
|
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: early morning | Statement: [Grand Couloir, bestCrossed, early morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestCrossed Context triple: [Grand Couloir, bestCrossed, early morning]
-
A.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
B.
crossedWith
Indicates that one entity has moved from one side of another entity or boundary to the opposite side, typically by passing over or through it.
-
C.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
D.
crossesIn
Indicates that one entity passes over or through the path, boundary, or area occupied by another entity, intersecting its space or trajectory.
-
E.
createdByCrossing
Indicates that something was produced as a result of crossing or hybridizing two or more distinct entities.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb62593c8190ab8462c4d9cd9d08 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef98ed84c81909dc86097df4afd4f |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:37 p.m.