Triple
T31295348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bibendum chair |
E798056
|
entity |
| Predicate | hasComfortLevel |
P203756
|
FINISHED |
| Object | plush |
—
|
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: plush | Statement: [Bibendum chair, hasComfortLevel, plush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComfortLevel Context triple: [Bibendum chair, hasComfortLevel, plush]
-
A.
relativeComfort
Indicates a comparative relationship where one entity is judged to be more or less comfortable than another under given conditions.
-
B.
comfort
Indicates providing physical or emotional ease, reassurance, or relief from distress to another entity.
-
C.
hadAutonomyLevel
Indicates the degree of independence or decision-making freedom an entity was allowed or exercised in a given context.
-
D.
hasConditionalityLevel
Indicates that one entity is associated with a specific degree or level of conditional requirements, constraints, or dependencies relative to another entity or context.
-
E.
hasSensibility
Indicates that an entity possesses awareness, responsiveness, or sensitivity to stimuli or experiences.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01e4ba62748190a4756689219b6269 |
completed | May 11, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_6a01e3fc2d908190a075c7c1549e5640 |
completed | May 11, 2026, 2:13 p.m. |
| PDg | Predicate description generation | batch_6a01e4b8f30c8190bca53f713ee0f901 |
completed | May 11, 2026, 2:16 p.m. |
Created at: April 29, 2026, 9:14 p.m.