Triple
T29389242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PrintDocumentAdapter |
E745331
|
entity |
| Predicate | onWrite |
P26267
|
FINISHED |
| Object | calledToWritePages |
—
|
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: calledToWritePages | Statement: [PrintDocumentAdapter, onWrite, calledToWritePages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onWrite Context triple: [PrintDocumentAdapter, onWrite, calledToWritePages]
-
A.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
-
B.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
C.
writingOutput
Indicates that one entity produces or generates written content as an output, typically as the result of a writing or text-creation process.
-
D.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
E.
writesTo
chosen
Indicates that one entity produces and records information, data, or content into another entity as a destination or storage target.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d578608190962d35116a01420c |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:41 p.m.