Triple
T10508681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexingtonians |
E247851
|
entity |
| Predicate | areResidentsOf |
P22499
|
FINISHED |
| Object | second-largest city in Kentucky |
—
|
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: second-largest city in Kentucky | Statement: [Lexingtonians, areResidentsOf, second-largest city in Kentucky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areResidentsOf Context triple: [Lexingtonians, areResidentsOf, second-largest city in Kentucky]
-
A.
hasResidenceIn
chosen
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
B.
residesNear
Indicates that one entity lives or is located in close physical proximity to another entity.
-
C.
isPermanentHomeOf
Indicates that a location serves as the long-term, primary residence for a particular entity.
-
D.
permanentResidents
Indicates that one entity is a long-term, officially recognized resident of another entity (such as a place, institution, or jurisdiction).
-
E.
residencyAt
Indicates that an entity lives or has an established residence at a particular location or address.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b287ac8190805a2375bd16b7ae |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:26 p.m.