Triple
T28866671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Steward |
E729018
|
entity |
| Predicate | presentsObject |
P180232
|
FINISHED |
| Object | a box with a button |
—
|
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: a box with a button | Statement: [Mr. Steward, presentsObject, a box with a button]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentsObject Context triple: [Mr. Steward, presentsObject, a box with a button]
-
A.
presentsView
Indicates that one entity displays or renders another entity as a view or visual interface to a user.
-
B.
presentedFor
Indicates that one entity was formally offered, submitted, or shown to another entity for consideration, review, or action.
-
C.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
-
D.
presentsAt
Indicates that one entity delivers or gives a presentation, talk, or performance at a particular event, venue, or occasion.
-
E.
hasPresentation
Indicates that an entity delivers, contains, or is associated with a specific presentation (such as a talk, slide deck, or formal display of information).
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 28, 2026, 6:49 a.m.