Triple
T18300730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPE (Multi-Agent Particle Environments) |
E438350
|
entity |
| Predicate | agentType |
P15045
|
FINISHED |
| Object | simple point-mass particles |
—
|
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: simple point-mass particles | Statement: [MPE (Multi-Agent Particle Environments), agentType, simple point-mass particles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agentType Context triple: [MPE (Multi-Agent Particle Environments), agentType, simple point-mass particles]
-
A.
storedAgentType
chosen
Indicates the type or category of agent that has been stored or recorded in association with an entity or event.
-
B.
agencyTypeOfOperator
Indicates the specific type or category of agency to which the operator belongs or by which the operator is characterized.
-
C.
hasAgent
Indicates that an action or event is carried out or initiated by a particular agent.
-
D.
assetOwnerType
Indicates the type or category of entity that owns or holds the asset.
-
E.
agency
Indicates that an entity acts on behalf of, represents, or exercises power or control for another entity in performing an action or fulfilling a role.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017f63dc819083a675d570620f2f |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.