Triple
T38443640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpyBoy |
E906574
|
entity |
| Predicate | hasWritingBy |
P185406
|
FINISHED |
| Object | Peter David |
—
|
NE NERFINISHED |
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: Peter David | Statement: [SpyBoy, hasWritingBy, Peter David]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWritingBy Context triple: [SpyBoy, hasWritingBy, Peter David]
-
A.
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.
-
B.
hasWriterOfWork
chosen
Indicates that a person or entity is the writer/author who created a particular work (such as a book, article, or script).
-
C.
hasWrittenAbout
Indicates that one entity has authored content or material discussing, analyzing, or referencing another entity.
-
D.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
E.
hasWritingAssociated
Indicates that there is a piece of writing (such as a text, document, or inscription) linked or connected to the given entity.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.