Triple
T30858056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Deadly Mantis |
E785981
|
entity |
| Predicate | mainMonster |
P18265
|
FINISHED |
| Object | giant prehistoric praying mantis |
—
|
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: giant prehistoric praying mantis | Statement: [The Deadly Mantis, mainMonster, giant prehistoric praying mantis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainMonster Context triple: [The Deadly Mantis, mainMonster, giant prehistoric praying mantis]
-
A.
mainMonsterDescription
chosen
Indicates the primary descriptive text that characterizes the main monster in a given context or scenario.
-
B.
featuresMonster
Indicates that something includes or prominently presents a monster as part of its content or composition.
-
C.
primaryEnemy
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
D.
primaryAntagonistSpeciesFaced
Indicates the species that serves as the main opposing or enemy group confronted by a given entity.
-
E.
associatedWithMonster
Indicates a relationship in which an entity is connected or linked in some notable way to a monster.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691a665c481908e0a9a2aef659563 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:46 p.m.