Triple
T30218354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weeksville |
E768269
|
entity |
| Predicate | hasHistoricHouses |
P133033
|
FINISHED |
| Object | Hunterfly Road Houses |
—
|
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: Hunterfly Road Houses | Statement: [Weeksville, hasHistoricHouses, Hunterfly Road Houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricHouses Context triple: [Weeksville, hasHistoricHouses, Hunterfly Road Houses]
-
A.
containsHistoricHouse
chosen
Indicates that one entity includes or encompasses a historic house within its boundaries or composition.
-
B.
housingTypeHistoric
Indicates that an entity’s housing type is classified based on historical or heritage-related characteristics.
-
C.
historicallyAssociatedHouse
Indicates that there is a historical connection or association between an entity and a particular house, such as residence, ownership, or significant events tied to that location.
-
D.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
E.
hasHistoricHut
Indicates that an entity possesses, contains, or is associated with a historic hut.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 29, 2026, 7:34 p.m.