Triple
T23004993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPC |
E572737
|
entity |
| Predicate | workflowStyle |
P117161
|
FINISHED |
| Object | pattern-based workflow |
—
|
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: pattern-based workflow | Statement: [MPC, workflowStyle, pattern-based workflow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workflowStyle Context triple: [MPC, workflowStyle, pattern-based workflow]
-
A.
typicalWorkflow
Indicates that one process, sequence, or set of actions represents the standard or commonly followed way of performing a task or achieving a goal.
-
B.
worksMethod
chosen
Indicates that one entity performs, operates, or functions using the method, technique, or procedure represented by the other entity.
-
C.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
-
D.
workDirector
Indicates that one entity serves as the director (creative or managerial lead) of a particular work or production associated with the other entity.
-
E.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18356417881908c8d6ee56bdc85f5 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.