Triple
T27476729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedmont (Georgia) |
E693482
|
entity |
| Predicate | stateRegionOf |
P115061
|
FINISHED |
| Object | Georgia Piedmont ecoregion |
—
|
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: Georgia Piedmont ecoregion | Statement: [Piedmont (Georgia), stateRegionOf, Georgia Piedmont ecoregion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateRegionOf Context triple: [Piedmont (Georgia), stateRegionOf, Georgia Piedmont ecoregion]
-
A.
stateOrRegion
chosen
Indicates that one entity is a state or region in which the other entity is located or with which it is associated.
-
B.
regionOfState
Indicates that one administrative or geographical region is a subdivision or part of a larger state.
-
C.
inUSStateRegion
Indicates that one entity is located within, or belongs to, a specific region of a U.S. state.
-
D.
stateElectoralRegion
Indicates the electoral district or region within a state that an entity is associated with for voting or representation purposes.
-
E.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 27, 2026, 12:57 p.m.