Triple
T33645321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Sheffield |
E861944
|
entity |
| Predicate | settingOfAuthoredWork |
P147158
|
FINISHED |
| Object | Texas |
—
|
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: Texas | Statement: [Edward Sheffield, settingOfAuthoredWork, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfAuthoredWork Context triple: [Edward Sheffield, settingOfAuthoredWork, Texas]
-
A.
settingOfWorks
Indicates that a place or environment serves as the primary setting where the events or narratives of one or more works take place.
-
B.
settingOfNotableWork
Indicates that a particular place or environment serves as the primary setting where a notable work (such as a book, film, or play) takes place.
-
C.
settingOfAuthority
Indicates that one entity serves as the context, domain, or environment within which another entity holds or exercises authority.
-
D.
hasAuthorOfWorkSetThere
chosen
Indicates that the location is a setting in a work created by the specified author.
-
E.
authorshipStatus
Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:42 a.m.