Triple
T36961417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morph Ovum |
E914316
|
entity |
| Predicate | cannotAffect |
P171474
|
FINISHED |
| Object | most boss monsters |
—
|
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: most boss monsters | Statement: [Morph Ovum, cannotAffect, most boss monsters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotAffect Context triple: [Morph Ovum, cannotAffect, most boss monsters]
-
A.
cannotBeInfluencedBy
chosen
Indicates that one entity is not susceptible to being affected, altered, or swayed by another entity or factor.
-
B.
cannot
Indicates that one entity lacks the ability, permission, or possibility to perform an action or participate in a specified relationship with another entity.
-
C.
cannotVeto
Indicates that an entity lacks the authority or ability to reject, block, or override a decision, proposal, or action made by another entity.
-
D.
cannotChange
Indicates that an entity is unable or not permitted to alter the state, value, or properties of another entity or relationship.
-
E.
cannotRestrict
Indicates that one entity lacks the authority, ability, or right to impose limits, constraints, or prohibitions on another entity or its actions.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.