Triple
T21422441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPI |
E528468
|
entity |
| Predicate | abstraction |
P143906
|
FINISHED |
| Object | communicator |
—
|
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: communicator | Statement: [MPI, abstraction, communicator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abstraction Context triple: [MPI, abstraction, communicator]
-
A.
primaryAbstraction
Indicates that one entity serves as the main conceptual generalization or core abstract representation of another entity.
-
B.
usesAbstraction
Indicates that one entity employs or relies on an abstract representation or interface of another entity rather than interacting with its concrete implementation directly.
-
C.
includesAbstract
Indicates that one entity contains or incorporates the abstract or summary section of another entity.
-
D.
providesAbstraction
Indicates that one entity offers a higher-level, simplified interface or conceptual layer that hides the underlying complexity of another entity.
-
E.
conceptualAspect
Indicates that one entity represents an abstract, conceptual, or non-physical aspect, feature, or dimension of 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2d17f5081908f0185011eae3160 |
completed | April 22, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:48 p.m.