Triple
T11007064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parrottsville, Tennessee |
E260144
|
entity |
| Predicate | historicSettlement |
P17528
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Parrottsville, Tennessee, historicSettlement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicSettlement Context triple: [Parrottsville, Tennessee, historicSettlement, true]
-
A.
historicAdministrativeCentre
Indicates that a place served as the main administrative or governmental center for a region or jurisdiction during a past historical period.
-
B.
historicCore
Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
-
C.
traditionalSettlement
chosen
Indicates that an entity is a settlement characterized by long-established, customary, or historically rooted patterns of habitation and land use.
-
D.
historicLocationType
Indicates the specific kind or category of a place based on its historical significance or role.
-
E.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79757bdcc8190900b267826eece21 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.