Triple
T32663342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiloh, Butler County, Alabama |
E835083
|
entity |
| Predicate | usesState |
P192659
|
FINISHED |
| Object | Alabama |
—
|
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: Alabama | Statement: [Shiloh, Butler County, Alabama, usesState, Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesState Context triple: [Shiloh, Butler County, Alabama, usesState, Alabama]
-
A.
usedInState
Indicates that something is employed, applied, or functions within a particular state or condition.
-
B.
usedByStateOrTerritory
Indicates that something (such as an object, system, or resource) is utilized or employed by a specific state or territory.
-
C.
stateIncludes
Indicates that a given state encompasses, contains, or has within its boundaries another specified entity or region.
-
D.
usedStateApparatus
Indicates that an entity employed or exploited the mechanisms, institutions, or powers of a state apparatus to achieve or support some action or outcome.
-
E.
inState
Indicates that an entity is currently located within or belongs to a particular state or condition.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 1, 2026, 1:08 a.m.