Triple
T24721208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugitive Poets |
E612300
|
entity |
| Predicate | editorialFigure |
P35804
|
FINISHED |
| Object | John Crowe Ransom |
—
|
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: John Crowe Ransom | Statement: [Fugitive Poets, editorialFigure, John Crowe Ransom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorialFigure Context triple: [Fugitive Poets, editorialFigure, John Crowe Ransom]
-
A.
discussesFigure
Indicates that one entity engages in discussion or analysis specifically about a particular figure (such as a person, character, or notable individual).
-
B.
editorialFormat
Indicates the specific editorial style, layout, or presentation format in which content is produced or published.
-
C.
editorialSupport
Indicates that one entity provides editorial assistance, guidance, or services to another entity or work.
-
D.
editorialRole
chosen
Indicates that one entity holds an editorial position or responsibility in relation to another entity, such as a publication, work, or organization.
-
E.
editorialLine
Indicates the overarching editorial stance, policy, or perspective that guides how content is selected, framed, and presented.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:40 a.m.