Triple
T35800468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak routes |
E1034959
|
entity |
| Predicate | typicalEndpointsInclude |
—
|
GENERATED |
| Object | Boston |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEndpointsInclude Context triple: [Amtrak routes, typicalEndpointsInclude, Boston]
-
A.
typicalEndpoint
chosen
Indicates that something represents the standard or commonly used endpoint associated with another entity or process.
-
B.
endpointInclusion
Indicates that one endpoint is contained within or is part of another endpoint or endpoint set.
-
C.
usesEndpoint
Indicates that one entity accesses or interacts with a specific endpoint to perform an operation or exchange data.
-
D.
typicalPositionsInclude
Indicates that certain positions or roles are commonly or characteristically included within something (such as an organization, structure, or context).
-
E.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
- F. None of above.
Provenance (1 batch)
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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.