Triple
T37514286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Road to Alcarnus |
E932593
|
entity |
| Predicate | hasWaypointNearby |
P99973
|
FINISHED |
| Object | Khasim Outpost Waypoint |
—
|
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: Khasim Outpost Waypoint | Statement: [Road to Alcarnus, hasWaypointNearby, Khasim Outpost Waypoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaypointNearby Context triple: [Road to Alcarnus, hasWaypointNearby, Khasim Outpost Waypoint]
-
A.
hasWaypoint
chosen
Indicates that an entity follows a path or route that includes a specific intermediate location (waypoint) along its trajectory.
-
B.
hasNearbyPoint
Indicates that one entity has at least one other point located within a specified proximity or distance from it.
-
C.
hasNearbyCrossingPoint
Indicates that one location has a crossing point (such as a bridge, crosswalk, or intersection) situated close to it.
-
D.
hasNearbyTrail
Indicates that one entity is located close to or within a short distance of a trail.
-
E.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:17 p.m.