Triple
T7233738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title Ten |
E154967
|
entity |
| Predicate | isWritten |
P75925
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Title Ten, isWritten, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWritten Context triple: [Title Ten, isWritten, yes]
-
A.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
-
B.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
C.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
D.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
E.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea552a688190a00f5d0ad982f787 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6ea539f5c81908001524149903559 |
completed | March 27, 2026, 8:36 p.m. |
Created at: March 27, 2026, 2:55 p.m.