Triple
T38634709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scrapyard |
E937545
|
entity |
| Predicate | hasFlankingRoute |
P192544
|
FINISHED |
| Object | outer edges of the map |
—
|
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: outer edges of the map | Statement: [Scrapyard, hasFlankingRoute, outer edges of the map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlankingRoute Context triple: [Scrapyard, hasFlankingRoute, outer edges of the map]
-
A.
hasFixedRoute
Indicates that an entity follows a predetermined, unchanging path or sequence of locations when operating or moving.
-
B.
hasRouteAlignment
Indicates that there is a defined spatial or geometric alignment associated with a route or pathway.
-
C.
hasAlongRoute
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
D.
hasRouteNetwork
Indicates that one entity possesses, is associated with, or is covered by a specific route network connecting multiple locations or paths.
-
E.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69fd0d0aebac8190868a7714ddb4f1fd |
completed | May 7, 2026, 10:07 p.m. |
Created at: May 3, 2026, 4:32 p.m.