Triple
T8895062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bed |
E211785
|
entity |
| Predicate | usesFoundObjects |
P82896
|
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: [Bed, usesFoundObjects, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFoundObjects Context triple: [Bed, usesFoundObjects, true]
-
A.
usesFoundObject
chosen
Indicates that an entity makes use of an object that it has previously found or discovered.
-
B.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
C.
containsObjectsBeyond
Indicates that a container or space holds additional objects beyond a specified set, limit, or boundary.
-
D.
containsFinding
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
-
E.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61be2c2081908f39cccdc149872d |
completed | April 1, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:54 p.m.