Triple
T34472651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quincy No. 2 Hoist House |
E884945
|
entity |
| Predicate | hasHoistType |
P194627
|
FINISHED |
| Object | steam hoist |
—
|
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: steam hoist | Statement: [Quincy No. 2 Hoist House, hasHoistType, steam hoist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHoistType Context triple: [Quincy No. 2 Hoist House, hasHoistType, steam hoist]
-
A.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
hasCastType
Indicates that an entity participates in a production with a specified type of casting role (e.g., lead, supporting, cameo).
-
C.
hasRootType
Indicates that an entity possesses or is associated with a primary or fundamental type that serves as its root classification.
-
D.
hasFlowType
Indicates the type or category of flow associated with or exhibited by an entity.
-
E.
hasParType
Indicates that an entity has a specific parent type or category to which it belongs.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
| PDg | Predicate description generation | batch_69fd7e35967081909f8bc8389d976ffd |
completed | May 8, 2026, 6:09 a.m. |
Created at: May 1, 2026, 2:01 a.m.