Triple
T8324412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walkern |
E194912
|
entity |
| Predicate | hasHistoricMillSite |
P2411
|
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: [Walkern, hasHistoricMillSite, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricMillSite Context triple: [Walkern, hasHistoricMillSite, true]
-
A.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
B.
hasHistoricMillVillageRoots
Indicates that something originates from or is historically connected to a traditional mill village community or heritage.
-
C.
isHistoricPlace
Indicates that a place holds recognized historical significance, often due to its age, events, or cultural importance.
-
D.
hasHistoricFarm
Indicates that an entity possesses, includes, or is associated with a farm that has historical significance or heritage value.
-
E.
hasIndustrialHeritage
chosen
Indicates that an entity possesses or is associated with historically significant industrial sites, structures, or practices.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f7e4f8081908e0f876ad962c932 |
completed | March 31, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.