Triple
T16722155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fearrington family |
E406374
|
entity |
| Predicate | localTo |
P100181
|
FINISHED |
| Object | Chatham County, North Carolina |
—
|
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: Chatham County, North Carolina | Statement: [Fearrington family, localTo, Chatham County, North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localTo Context triple: [Fearrington family, localTo, Chatham County, North Carolina]
-
A.
isLocalTo
chosen
Indicates that one entity is geographically or contextually situated near, or within the same local area or scope as, another entity.
-
B.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
-
C.
localTimeOf
Indicates the specific local time associated with a given entity, typically relative to its geographic location or time zone.
-
D.
localFactorAt
Indicates a relationship where a specific factor or influence is associated with, or applies at, a particular local point, position, or context.
-
E.
localTime
Indicates that a specific time value is expressed relative to a particular local time zone or locale, rather than in a universal or standardized time reference.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e387449eb08190b174f8e142ea631b |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.