Triple
T22309311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APT-S |
E551470
|
entity |
| Predicate | intendedRouteType |
P75679
|
FINISHED |
| Object | high-speed main line |
—
|
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: high-speed main line | Statement: [APT-S, intendedRouteType, high-speed main line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRouteType Context triple: [APT-S, intendedRouteType, high-speed main line]
-
A.
primaryRouteType
chosen
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
-
B.
routePurpose
Indicates the intended function or goal that a particular route is designed or used to serve.
-
C.
usesRoutingType
Indicates that one entity employs or operates according to a specific routing type or routing method associated with another entity.
-
D.
notableRouteType
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
-
E.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574d53148190a1ec07f849e1ae9d |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.