Triple
T8745350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trencherfield Mill |
E207811
|
entity |
| Predicate | engineUse |
P56323
|
FINISHED |
| Object | powering mill machinery |
—
|
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: powering mill machinery | Statement: [Trencherfield Mill, engineUse, powering mill machinery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineUse Context triple: [Trencherfield Mill, engineUse, powering mill machinery]
-
A.
engineTypeUsed
chosen
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
B.
engineName
Indicates the specific name assigned to an engine associated with an entity.
-
C.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
D.
engineClass
Indicates the classification or type category assigned to an engine within a given system or context.
-
E.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d745e0081909cab216593d5c01b |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:38 p.m.