Triple
T24562478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George W. Featherstonhaugh |
E607691
|
entity |
| Predicate | surveyedRegion |
P90123
|
FINISHED |
| Object | Arkansas Territory |
—
|
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: Arkansas Territory | Statement: [George W. Featherstonhaugh, surveyedRegion, Arkansas Territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveyedRegion Context triple: [George W. Featherstonhaugh, surveyedRegion, Arkansas Territory]
-
A.
surveyRegion
chosen
Indicates that an entity conducts or pertains to a survey covering a specified geographic or administrative region.
-
B.
surveyedIn
Indicates that an entity was included as part of the scope or coverage of a particular survey or data-collection effort.
-
C.
studiesRegion
Indicates that an entity engages in the academic or systematic study of a particular geographic or cultural region.
-
D.
represented region
Indicates that one entity serves as a symbolic or formal depiction of a specific geographic or spatial area.
-
E.
primarySurveyArea
Indicates that a specified area is the main or principal region targeted or covered by a particular survey or data collection activity.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f7a244819080596718c21d0df3 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.