Triple
T20319264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIX |
E492163
|
entity |
| Predicate | usedInBaggageTagging |
P34623
|
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: [RIX, usedInBaggageTagging, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInBaggageTagging Context triple: [RIX, usedInBaggageTagging, true]
-
A.
usedInBaggageTags
chosen
Indicates that something (such as a code, identifier, or element) is employed or printed on baggage tags for identification or processing purposes.
-
B.
hasBaggageClaim
Indicates that a location, typically a transportation hub, includes or provides a baggage claim area for retrieving luggage.
-
C.
hasCheckedBaggage
Indicates that an entity is associated with baggage that has been checked in for transport, typically for a trip or flight.
-
D.
usedInPriceTags
Indicates that something is employed or referenced in the creation, display, or calculation of price tags.
-
E.
hasBaggageService
Indicates that an entity provides or supports services related to handling, storing, or managing baggage for others.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778abd14819098a01fd32217fdde |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b23a0788190bf1853ef5b81823f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:20 a.m.