Triple
T22041449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WOD |
E544644
|
entity |
| Predicate | oftenPostedOn |
P145584
|
FINISHED |
| Object | whiteboard |
—
|
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: whiteboard | Statement: [WOD, oftenPostedOn, whiteboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenPostedOn Context triple: [WOD, oftenPostedOn, whiteboard]
-
A.
oftenFormulatedOn
Indicates that something (such as a statement, plan, or decision) is frequently based on, derived from, or constructed using another thing as its foundation or starting point.
-
B.
postedIn
Indicates that a piece of content or message was submitted or shared within a particular forum, group, channel, or location.
-
C.
oftenFrom
chosen
Indicates that something frequently originates, derives, or comes from a particular source or location.
-
D.
laterPosting
Indicates that one posting, message, or publication occurs at a later time than another in a temporal sequence.
-
E.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12829c1c081909edc7544242c9c7a |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.