Triple
T3124182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woolsey, Georgia |
E65255
|
entity |
| Predicate | isSmallTown |
P17862
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Woolsey, Georgia, isSmallTown, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSmallTown Context triple: [Woolsey, Georgia, isSmallTown, true]
-
A.
isSmallCity
chosen
Indicates that a city has a relatively small population size or limited geographic/urban extent compared to typical cities.
-
B.
isSmallAreaMunicipality
Indicates that a municipality is classified as a small-area municipality, typically based on limited geographic size or population.
-
C.
isInlandTown
Indicates that a town is located away from the coast, without direct access to the sea or ocean.
-
D.
isSmallScale
Indicates that the related activity, operation, or entity occurs on a limited or minor scale, involving relatively small size, scope, or capacity.
-
E.
isSuburbanCommunity
Indicates that a community is located in a suburban area, typically characterized by residential neighborhoods situated between urban centers and rural regions.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada52d856c8190a5d65b8a6452be21 |
completed | March 8, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.