Triple
T18033735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stickies |
E431452
|
entity |
| Predicate | ceasedMajorOperationsBy |
P114836
|
FINISHED |
| Object | mid-1970s |
—
|
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: mid-1970s | Statement: [Stickies, ceasedMajorOperationsBy, mid-1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedMajorOperationsBy Context triple: [Stickies, ceasedMajorOperationsBy, mid-1970s]
-
A.
ceasedOperationsDuring
chosen
Indicates that an entity stopped functioning or carrying out its activities at some point within the specified time period.
-
B.
ceasedOperationsAs
Indicates that an entity stopped functioning or operating in a particular role, capacity, or status.
-
C.
majorOperationsOf
Indicates that one entity is a primary or significant operation, activity, or functional undertaking associated with another entity.
-
D.
ceasedOperationAfter
Indicates that one entity stopped functioning, operating, or being active after another specified event or entity’s operation ended.
-
E.
ceasedOperation
Indicates that an entity has stopped functioning, operating, or carrying out its activities, typically in a permanent or indefinite manner.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be38766c8190ae95701f4575469c |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.