Triple
T31218579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stretch |
E795937
|
entity |
| Predicate | automationType |
P171035
|
FINISHED |
| Object | goods handling automation |
—
|
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: goods handling automation | Statement: [Stretch, automationType, goods handling automation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: automationType Context triple: [Stretch, automationType, goods handling automation]
-
A.
automatedIn
Indicates that an action, process, or operation is performed automatically within or by a specified system, context, or environment.
-
B.
automatedBy
Indicates that an action, process, or function is carried out or controlled by an automated system or mechanism.
-
C.
canAutomate
Indicates that one entity has the capability to perform, control, or execute another entity’s process or task automatically without continuous human intervention.
-
D.
automationLevel
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
E.
automationProtocol
Indicates that an entity follows or is governed by a defined set of automated procedures or rules for performing a task or process.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c4a700c81908ee61dcb01bffe50 |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 29, 2026, 9:10 p.m.