Triple
T31220898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon Barrett |
E796005
|
entity |
| Predicate | wroteSegmentFor |
P11775
|
FINISHED |
| Object | V/H/S |
—
|
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: V/H/S | Statement: [Simon Barrett, wroteSegmentFor, V/H/S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteSegmentFor Context triple: [Simon Barrett, wroteSegmentFor, V/H/S]
-
A.
wroteSectionOn
Indicates that one entity is the author or creator of a specific section within another entity (such as a document, book, or article).
-
B.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
-
C.
writtenForEvent
Indicates that something (typically a work or piece) was created specifically for a particular event or occasion.
-
D.
hasWrittenFor
chosen
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.
-
E.
laterWrittenDownAs
Indicates that something was recorded or documented in written form at a subsequent time after its original occurrence or expression.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c4d35848190bd5a2dd81851bea3 |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.