Triple
T24478228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fern Gayden |
E617290
|
entity |
| Predicate | editorFor |
P107303
|
FINISHED |
| Object | Negro Story |
—
|
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: Negro Story | Statement: [Fern Gayden, editorFor, Negro Story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorFor Context triple: [Fern Gayden, editorFor, Negro Story]
-
A.
intendedEditor
Indicates that one entity is designated or expected to act as the editor of another entity (such as a document, work, or content).
-
B.
editorOfWork
chosen
Indicates that one entity serves as the editor responsible for preparing, revising, or overseeing the content of a particular work.
-
C.
editorName
Indicates the relationship that specifies the name of an editor associated with a given entity.
-
D.
editorCommunity
Indicates a relationship where an editor is associated with, participates in, or belongs to a particular community.
-
E.
editorStart
Indicates the point in time or position at which an editor begins working on, modifying, or reviewing a content item or resource.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29ed3fce88190b5be7e085ef88c97 |
completed | April 30, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:21 a.m.