Triple
T13729231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vaquita marina |
E329747
|
entity |
| Predicate | principalAmenaza |
P23662
|
FINISHED |
| Object | captura incidental en redes de enmalle |
—
|
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: captura incidental en redes de enmalle | Statement: [vaquita marina, principalAmenaza, captura incidental en redes de enmalle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalAmenaza Context triple: [vaquita marina, principalAmenaza, captura incidental en redes de enmalle]
-
A.
primaryThreat
chosen
Indicates that one entity is the main or most significant source of danger, harm, or risk to another entity.
-
B.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
C.
primaryEnemy
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
D.
primaryAdversaryImplied
Indicates that an entity is understood or suggested, rather than explicitly stated, to be the main opponent or chief adversary of another entity.
-
E.
primaryAdversaryContext
Indicates the main opposing force or conflict-driving element that defines the central adversarial situation 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f746cc8190abde237bbb7e6c78 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.