Triple
T8745368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trencherfield Mill |
E207811
|
entity |
| Predicate | hasPreservedMachinery |
P85152
|
FINISHED |
| Object | steam engine |
—
|
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 engine | Statement: [Trencherfield Mill, hasPreservedMachinery, steam engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreservedMachinery Context triple: [Trencherfield Mill, hasPreservedMachinery, steam engine]
-
A.
hasPreservationActivity
Indicates that an entity is involved in, or associated with, a specific preservation-related action or process.
-
B.
hasSubjectOfPreservation
Indicates that something is the specific focus or object being preserved or conserved within a preservation relationship.
-
C.
hasPreservationType
Indicates the specific method or category of preservation applied to an entity (e.g., how it is stored, conserved, or kept intact).
-
D.
hasRestoration
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
E.
hasPreservationConditions
Indicates the specific environmental or handling conditions required to properly preserve or maintain an entity.
- 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_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. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:38 p.m.