Triple
T24197158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Page-A-Day calendars |
E599864
|
entity |
| Predicate | hasPageAction |
P155146
|
FINISHED |
| Object | tear off |
—
|
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: tear off | Statement: [Page-A-Day calendars, hasPageAction, tear off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPageAction Context triple: [Page-A-Day calendars, hasPageAction, tear off]
-
A.
hasPage
Indicates that one entity includes, is associated with, or is documented by a specific page (such as a web page or document page).
-
B.
hasActionType
Indicates that an action or event is classified as belonging to a specific type or category of actions.
-
C.
hasOwnerAction
Indicates that an owner performs, initiates, or is responsible for a specific action related to the owned entity.
-
D.
hasKeyAction
Indicates that an entity performs or is associated with a primary or essential action within a given context.
-
E.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24c103481908ea49dd8e77dee32 |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:36 p.m.