Triple
T37973652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawn Wall |
E947361
|
entity |
| Predicate | routeOpener |
P23654
|
FINISHED |
| Object | Tommy Caldwell |
—
|
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: Tommy Caldwell | Statement: [Dawn Wall, routeOpener, Tommy Caldwell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeOpener Context triple: [Dawn Wall, routeOpener, Tommy Caldwell]
-
A.
routeOperator
Indicates that an agent operates, manages, or is responsible for running a particular route or service path.
-
B.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
C.
openedRouteThrough
chosen
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
-
D.
openedAsThroughRoute
Indicates that a route or service began operating as a continuous through connection, rather than as separate or terminating segments.
-
E.
openedRouteBetween
Indicates that an agent initiated or established a route or connection enabling movement or communication between two locations or entities.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.