Triple
T38472594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millerton |
E915459
|
entity |
| Predicate | wasCountySeatUntil |
P191163
|
FINISHED |
| Object | 1874 |
—
|
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: 1874 | Statement: [Millerton, wasCountySeatUntil, 1874]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCountySeatUntil Context triple: [Millerton, wasCountySeatUntil, 1874]
-
A.
existedAsCountyUntil
Indicates that an entity functioned with the status or designation of a county up to a specified end date or time period.
-
B.
usedAsCountyNameUntil
Indicates that an entity served as the official name of a county up to a specified point in time.
-
C.
hasCountySeatSuccessor
Indicates that one county seat has been succeeded or replaced by another as the official administrative center for a county.
-
D.
countySeatSince
Indicates that one place has served as the official county seat of a county starting from a specified point in time.
-
E.
servedAsStateCapitalUntil
Indicates that a location functioned as the official capital of a state up to a specified end date.
- F. None of above. chosen
Provenance (4 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:31 p.m.