Triple
T24019311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp III |
E594770
|
entity |
| Predicate | routeContinuationTo |
P29764
|
FINISHED |
| Object | Camp IV (South Col) |
—
|
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: Camp IV (South Col) | Statement: [Camp III, routeContinuationTo, Camp IV (South Col)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeContinuationTo Context triple: [Camp III, routeContinuationTo, Camp IV (South Col)]
-
A.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
B.
routeUnder
Indicates that one route passes beneath another route or structure, typically at an underpass or similar crossing.
-
C.
nextRoute
Indicates that one route directly follows another in a defined sequence or ordering of routes.
-
D.
routeTargeted
Indicates that a route is specifically directed toward or intended to reach a particular target entity or destination.
-
E.
routeExtension
chosen
Indicates that an existing route is extended beyond its original endpoint to cover additional segments or destinations.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a925208190badd075519a0f4b6 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.