Triple
T20145990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komagata Maru incident |
E491303
|
entity |
| Predicate | passengersOrigin |
P1521
|
FINISHED |
| Object | Punjab region of British India |
—
|
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: Punjab region of British India | Statement: [Komagata Maru incident, passengersOrigin, Punjab region of British India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengersOrigin Context triple: [Komagata Maru incident, passengersOrigin, Punjab region of British India]
-
A.
hasOriginAirport
Indicates that something, typically a flight or journey, departs from or is associated with a specific origin airport.
-
B.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
C.
originAirportHub
Indicates that the referenced airport serves as a primary hub or main operating base for the associated airline or carrier.
-
D.
placeOfDeparture
chosen
Indicates the location from which an entity, such as a person or vehicle, begins its journey or movement.
-
E.
voyageOriginCountry
Indicates the country from which a voyage departs or originates.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679e43a48190b3a5da5710b07ff7 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.