Triple
T37664759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warped Forest |
E937795
|
entity |
| Predicate | hasParticle |
P3639
|
FINISHED |
| Object | warped spore |
—
|
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: warped spore | Statement: [Warped Forest, hasParticle, warped spore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticle Context triple: [Warped Forest, hasParticle, warped spore]
-
A.
hasParticleType
chosen
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
-
B.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
C.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
D.
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.
-
E.
hasParticularIn
Indicates that one entity possesses or exhibits a specific instance, form, or occurrence of another entity within a given context.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0061454944819088a0babfe60f69fc |
completed | May 10, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_6a0060b9ee108190b91e8d99a16f2b30 |
completed | May 10, 2026, 10:40 a.m. |
Created at: May 3, 2026, 4:18 p.m.