Triple
T24191024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RB14 |
E599695
|
entity |
| Predicate | passengerCategory |
P8370
|
FINISHED |
| Object | commuters |
—
|
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: commuters | Statement: [RB14, passengerCategory, commuters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerCategory Context triple: [RB14, passengerCategory, commuters]
-
A.
passengerCapacityCategory
Indicates the classification of an entity based on the number of passengers it is designed or allowed to carry.
-
B.
hasPassengerUsageCategory
chosen
Indicates the classification of how a passenger-related resource or service is used (e.g., its usage type or category for passengers).
-
C.
appliesToPassengerType
Indicates that a rule, condition, or attribute is relevant or restricted to a specific type or category of passenger.
-
D.
aircraftSeatingCategory
Indicates the classification of an aircraft’s seating arrangement or capacity type associated with an entity.
-
E.
passengerCount
Indicates the number of passengers associated with a given entity, such as a vehicle or trip.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:35 p.m.