Triple
T13278809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N106US |
E316262
|
entity |
| Predicate | passengersDuringEvent |
P882
|
FINISHED |
| Object | 150 |
—
|
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: 150 | Statement: [N106US, passengersDuringEvent, 150]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengersDuringEvent Context triple: [N106US, passengersDuringEvent, 150]
-
A.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
B.
passengersCountApproximate
chosen
Indicates that the number of passengers involved is given as an approximate or estimated count rather than an exact figure.
-
C.
capacityDuringEvent
Indicates the maximum number of occupants or usage level that a place, system, or resource can handle specifically during a given event.
-
D.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
E.
ticketedAudience
Indicates that the audience for an event or activity is required to obtain tickets (i.e., attendance is controlled or limited via ticketing).
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.