Triple
T9806674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiregrass |
E237969
|
entity |
| Predicate | hasPrimaryStatePortion |
P16690
|
FINISHED |
| Object | southeastern Alabama |
—
|
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: southeastern Alabama | Statement: [Wiregrass, hasPrimaryStatePortion, southeastern Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryStatePortion Context triple: [Wiregrass, hasPrimaryStatePortion, southeastern Alabama]
-
A.
hasStatePortionIn
chosen
Indicates that a state has a geographic portion or area located within the boundaries of another region or entity.
-
B.
hasPrimaryStateServed
Indicates that an entity has served or operated primarily within a specified state or state-level jurisdiction.
-
C.
hasPrimaryConstituent
Indicates that one entity serves as the main or principal component, ingredient, or element of another entity.
-
D.
hasPortionDesignatedAs
Indicates that one entity has a specific part or segment that is explicitly identified or designated as another entity.
-
E.
hasPrimaryCode
Indicates that an entity is associated with its main or most important identifying code among potentially multiple codes.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7cb9588190953a063cb7b9e29e |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.