Triple
T34586192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Radley |
E888049
|
entity |
| Predicate | subjectOfRumors |
P193960
|
FINISHED |
| Object | Maycomb children |
—
|
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: Maycomb children | Statement: [Arthur Radley, subjectOfRumors, Maycomb children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfRumors Context triple: [Arthur Radley, subjectOfRumors, Maycomb children]
-
A.
notableStorySubject
Indicates that the subject is a prominent or central topic, character, or element within a particular story or narrative.
-
B.
rumorContent
Indicates that the associated information specifies the subject matter or details contained within a particular rumor.
-
C.
conspiracyType
Indicates the specific category or nature of a conspiracy associated with an entity or event.
-
D.
hasBeenSubjectOf
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
-
E.
rumoredTarget
Indicates that an entity is believed or speculated, based on rumor or unconfirmed information, to be the intended target of another entity or action.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: May 1, 2026, 2:03 a.m.