Triple
T9505746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manila–New York |
E229263
|
entity |
| Predicate | requiresPassportForMostPassengers |
P85720
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Manila–New York, requiresPassportForMostPassengers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPassportForMostPassengers Context triple: [Manila–New York, requiresPassportForMostPassengers, true]
-
A.
fareRequired
Indicates that a payment or fare is required for access to or use of a service, route, or transportation option.
-
B.
hasPassengerRole
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
-
C.
passengerPolicy
chosen
Indicates the rules or conditions governing whether and how passengers are allowed or managed in a given context.
-
D.
canHoldPassport
Indicates that an entity is legally eligible or permitted to possess a passport.
-
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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9852b7e48190a8f69cbde10d2858 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.