Triple
T30098894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1867 Quaker City excursion |
E764938
|
entity |
| Predicate | numberOfPassengersApproximate |
P882
|
FINISHED |
| Object | 60 to 75 |
—
|
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: 60 to 75 | Statement: [1867 Quaker City excursion, numberOfPassengersApproximate, 60 to 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPassengersApproximate Context triple: [1867 Quaker City excursion, numberOfPassengersApproximate, 60 to 75]
-
A.
passengersCountApproximate
chosen
Indicates that the number of passengers involved is given as an approximate or estimated count rather than an exact figure.
-
B.
passengerCount
Indicates the number of passengers associated with a given entity, such as a vehicle or trip.
-
C.
crewAndPassengersCount
Indicates the total number of people on a vehicle or vessel, combining both crew members and passengers.
-
D.
maximumPassengerCapacity
Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
-
E.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0045a7b4c081908e4dedabda7cf790 |
completed | May 10, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_6a0042b148a48190974b173f352e4b7f |
completed | May 10, 2026, 8:32 a.m. |
Created at: April 29, 2026, 7:08 p.m.