Triple
T17776766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amoskeag Manufacturing Company |
E443789
|
entity |
| Predicate | builtHousingFor |
P43310
|
FINISHED |
| Object | mill workers |
—
|
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: mill workers | Statement: [Amoskeag Manufacturing Company, builtHousingFor, mill workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtHousingFor Context triple: [Amoskeag Manufacturing Company, builtHousingFor, mill workers]
-
A.
buildingAlsoHouses
Indicates that a building additionally contains or accommodates another function, entity, or activity beyond its primary purpose.
-
B.
builtProperty
Indicates that a constructed structure or building has been created on, or is associated with, a particular property or piece of land.
-
C.
houseProduced
chosen
Indicates that a house or housing unit was created, built, or generated by a particular agent, process, or source.
-
D.
architectOfOwnedHouses
Indicates that an entity serves as the architect or designer of houses that are owned by another specified entity.
-
E.
builtNear
Indicates that one entity was constructed at a location geographically close to another entity.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4871d43a481908aacde69bd8091b0 |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.