Triple
T36914673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABZ |
E913011
|
entity |
| Predicate | isPrintedOnBoardingPass |
P87530
|
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: [ABZ, isPrintedOnBoardingPass, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrintedOnBoardingPass Context triple: [ABZ, isPrintedOnBoardingPass, true]
-
A.
isBoardingRequired
Indicates that an entity must undergo a boarding process (such as embarking onto a vehicle, vessel, or platform) as a required step or condition.
-
B.
isPrinted
chosen
Indicates that a physical copy of an item has been produced using a printing process.
-
C.
isBoarding
Indicates that an entity is in the process of getting onto or entering a vehicle, vessel, or similar mode of transport.
-
D.
hasBoardingType
Indicates the specific manner or method by which an entity is boarded or accessed (e.g., how passengers or items are taken on).
-
E.
imprintedOn
Indicates that one entity has formed a strong, often early-life, attachment or bond to another entity, typically treating it as a primary reference or caregiver.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:13 p.m.