Triple
T6017647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak Carolinian |
E133985
|
entity |
| Predicate | offersBicycleCarriage |
P47469
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Amtrak Carolinian, offersBicycleCarriage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersBicycleCarriage Context triple: [Amtrak Carolinian, offersBicycleCarriage, true]
-
A.
hasRideCycle
Indicates that one entity is associated with, or participates in, a recurring sequence or cycle of rides or ride operations.
-
B.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
C.
carriageType
chosen
Indicates the specific kind or category of carriage associated with or used in relation to an entity.
-
D.
rideSystem
Indicates that one entity uses or travels on a transportation system or service provided by another entity.
-
E.
hasRideSystem
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f8458588190a78aa32cbdbecfb1 |
completed | March 22, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.