Triple
T30933047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World's Best Boss mug |
E788045
|
entity |
| Predicate | propStatus |
P149065
|
FINISHED |
| Object | recognizable TV prop |
—
|
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: recognizable TV prop | Statement: [World's Best Boss mug, propStatus, recognizable TV prop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propStatus Context triple: [World's Best Boss mug, propStatus, recognizable TV prop]
-
A.
propState
chosen
Indicates that an entity possesses, is in, or exhibits a particular state or condition.
-
B.
propertyStatus
Indicates the current condition, state, or classification assigned to a property within a given context (e.g., availability, legal standing, or operational state).
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
proposerState
Indicates the current status or condition of a proposer within a proposal or decision-making process.
-
E.
actStatus
Indicates the current state or condition of an action or event, such as whether it is planned, ongoing, completed, or cancelled.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692e1aef48190b8ac1b2027013d94 |
completed | May 3, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:52 p.m.