Triple
T2658976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Dawson |
E54680
|
entity |
| Predicate | modeOfBoarding |
P18241
|
FINISHED |
| Object | won ticket in poker game |
—
|
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: won ticket in poker game | Statement: [Jack Dawson, modeOfBoarding, won ticket in poker game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfBoarding Context triple: [Jack Dawson, modeOfBoarding, won ticket in poker game]
-
A.
hasBoardingType
chosen
Indicates the specific manner or method by which an entity is boarded or accessed (e.g., how passengers or items are taken on).
-
B.
hasBoardingAreaFor
Indicates that one entity provides or contains a designated area where passengers can board another entity (such as a vehicle or vessel).
-
C.
airportAccessMode
Indicates the typical mode or method of transportation used to access or reach an airport.
-
D.
boarding
Indicates that one entity is getting onto or entering a vehicle, vessel, or similar conveyance associated with another entity.
-
E.
passengerAccess
Indicates that a passenger is allowed to enter, use, or move through a particular vehicle, area, or transportation-related facility.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94dcaa48190aec625f68ce61a02 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.