Triple
T15695703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galapagos shark |
E380453
|
entity |
| Predicate | exploitedFor |
P120322
|
FINISHED |
| Object | meat |
—
|
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: meat | Statement: [Galapagos shark, exploitedFor, meat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploitedFor Context triple: [Galapagos shark, exploitedFor, meat]
-
A.
exploitationBegan
Indicates the point in time when the exploitation or use of a resource, person, or system was initiated.
-
B.
exploits
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
-
C.
эксплуатируется
Indicates that one entity is being used or operated by another, often in a way that takes advantage of its resources, capabilities, or labor.
-
D.
usedForcedLabor
Indicates that an entity compelled people to work against their will, typically under coercion, threat, or without fair compensation.
-
E.
usedByPerpetrators
Indicates that something (e.g., a tool, method, or resource) is employed or utilized by perpetrators in carrying out their actions.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0b4d01c9c81909f6b611e8144c838 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 10, 2026, 4:44 a.m.