Triple
T14927939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Austell, Georgia (part) |
E372179
|
entity |
| Predicate | isPortionDefinedBy |
P70125
|
FINISHED |
| Object | Douglas County boundary |
—
|
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: Douglas County boundary | Statement: [City of Austell, Georgia (part), isPortionDefinedBy, Douglas County boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPortionDefinedBy Context triple: [City of Austell, Georgia (part), isPortionDefinedBy, Douglas County boundary]
-
A.
hasPortionDesignatedAs
Indicates that one entity has a specific part or segment that is explicitly identified or designated as another entity.
-
B.
containsPortionOf
Indicates that one entity includes or holds a part, segment, or fraction of another entity.
-
C.
hasStatePortionIn
Indicates that a state has a geographic portion or area located within the boundaries of another region or entity.
-
D.
includesPort
Indicates that one entity contains, encompasses, or has as part of it a specific port or set of ports.
-
E.
isPartially
chosen
Indicates that one entity is included within another to some extent, but not completely or fully.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded634e67881909daec9eaef188d09 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:35 a.m.