Triple
T14609849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak train 63 |
E342927
|
entity |
| Predicate | crossBorderService |
P95603
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Amtrak train 63, crossBorderService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderService Context triple: [Amtrak train 63, crossBorderService, yes]
-
A.
crossBorderTradeHub
Indicates a location or entity that serves as a central point for facilitating, coordinating, or processing trade activities that occur across national or regional borders.
-
B.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
C.
isCrossBorder
chosen
Indicates that the relationship or action involves entities located in or spanning across different national or jurisdictional boundaries.
-
D.
crossBorderPartner
Indicates a partnership relationship between entities that operate across national or jurisdictional borders.
-
E.
crossBorderLinks
Indicates connections or interactions that extend across or link entities in different geographic or political jurisdictions.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44f0dd48190a78662b5998a6722 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.