Triple
T1268204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolesville |
E15649
|
entity |
| Predicate | relativeSizeInCounty |
P24333
|
FINISHED |
| Object | small town |
—
|
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: small town | Statement: [Rolesville, relativeSizeInCounty, small town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSizeInCounty Context triple: [Rolesville, relativeSizeInCounty, small town]
-
A.
populationRankInCounty
chosen
Indicates the relative position of an entity in terms of population size compared to other entities within the same county.
-
B.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
C.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
D.
isInCountySeatProximity
Indicates that one location lies within a defined close distance to the county seat of a given county.
-
E.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c0396e048190b4e2d7aab19268b3 |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.