Triple
T11659017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enderman |
E277076
|
entity |
| Predicate | emitsParticles |
P1456
|
FINISHED |
| Object | purple portal-like 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: purple portal-like particles | Statement: [Enderman, emitsParticles, purple portal-like particles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emitsParticles Context triple: [Enderman, emitsParticles, purple portal-like particles]
-
A.
involvesParticleEjection
chosen
Indicates that the action or process includes the emission or release of particles from a source.
-
B.
usedParticle
Indicates that one entity employs or applies a particular particle (e.g., subatomic, linguistic, or material) in some process, context, or construction involving another entity.
-
C.
emitsSpectrum
Indicates that one entity produces or gives off electromagnetic radiation characterized by a particular spectrum.
-
D.
emitted
Indicates that one entity has released, discharged, or sent out another entity, such as energy, particles, signals, or substances, into its surroundings.
-
E.
eruptionEffect
Indicates the impact or consequences that an eruption has on its surrounding environment, systems, or entities.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.