Triple
T26232216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albury Mill |
E656061
|
entity |
| Predicate | hasMillingOperations |
P166607
|
FINISHED |
| Object | traditional milling operations |
—
|
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: traditional milling operations | Statement: [Albury Mill, hasMillingOperations, traditional milling operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMillingOperations Context triple: [Albury Mill, hasMillingOperations, traditional milling operations]
-
A.
hasMainOperations
Indicates that an entity is associated with its primary or core operations, activities, or functions.
-
B.
hasTypeOfMill
Indicates that an entity is associated with or characterized by a specific type or category of mill.
-
C.
hasMill
Indicates that an entity possesses, contains, or is associated with a mill (e.g., as an owner, host location, or site).
-
D.
hasOperationsIn
Indicates that an entity conducts business activities or maintains operational presence within a specified location or region.
-
E.
hasRefiningOperations
Indicates that one entity performs or is associated with refining processes or operations applied to another 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 26, 2026, 9 p.m.