Triple
T33545757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scorpaena |
E859200
|
entity |
| Predicate | ambushStrategy |
P176875
|
FINISHED |
| Object | sit-and-wait predator |
—
|
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: sit-and-wait predator | Statement: [Scorpaena, ambushStrategy, sit-and-wait predator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambushStrategy Context triple: [Scorpaena, ambushStrategy, sit-and-wait predator]
-
A.
ambushParticipant
Indicates that an entity takes part in an ambush, either as an attacker or as a target within that ambush event.
-
B.
surpriseAttack
Indicates an aggressive action initiated unexpectedly against a target that is unprepared or unaware.
-
C.
plannedAttackWith
Indicates that one entity has prepared or organized an attack using or involving another entity as the means or instrument of that attack.
-
D.
plannedAttack
Indicates that an entity has intentionally prepared and organized an attack against a target.
-
E.
methodOfInvasion
Indicates the specific way or technique by which an invasion is carried out.
- F. None of above. chosen
Provenance (4 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:39 a.m.