Triple
T17819047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alderson, West Virginia |
E444924
|
entity |
| Predicate | originalSettlementFunction |
P129021
|
FINISHED |
| Object | river 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: river town | Statement: [Alderson, West Virginia, originalSettlementFunction, river town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSettlementFunction Context triple: [Alderson, West Virginia, originalSettlementFunction, river town]
-
A.
originalSettlement
Indicates that one entity is the initial or first-established settlement location associated with another entity.
-
B.
originalSettlementName
Indicates the name by which a settlement was originally known before any later renaming or reclassification.
-
C.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
D.
primarySettlementOrigin
Indicates that one settlement is the main or original source from which another settlement was founded or developed.
-
E.
organizedSettlement
Indicates that an entity actively planned, coordinated, and arranged the establishment or occurrence of a settlement.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e488812df081909771d51c54c405fe |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:15 a.m.