Triple
T32040646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axiom |
E818209
|
entity |
| Predicate | passengerCondition |
P179839
|
FINISHED |
| Object | state of perpetual leisure |
—
|
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: state of perpetual leisure | Statement: [Axiom, passengerCondition, state of perpetual leisure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerCondition Context triple: [Axiom, passengerCondition, state of perpetual leisure]
-
A.
appliesToPassengerType
Indicates that a rule, condition, or attribute is relevant or restricted to a specific type or category of passenger.
-
B.
passengerPolicy
Indicates the rules or conditions governing whether and how passengers are allowed or managed in a given context.
-
C.
isPassengerWith
Indicates that one entity is traveling together with another entity as a passenger in the same vehicle or conveyance.
-
D.
hasPassengerAmenity
Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
-
E.
passengersType
Indicates the type or category of passengers associated with or involved in a given entity or context.
- F. None of above. chosen
Provenance (4 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 12:19 a.m.