Triple
T27750293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS10-021 |
E702096
|
entity |
| Predicate | exploitationPossible |
P165408
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MS10-021, exploitationPossible, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploitationPossible Context triple: [MS10-021, exploitationPossible, yes]
-
A.
exploitationBegan
Indicates the point in time when the exploitation or use of a resource, person, or system was initiated.
-
B.
exploitedFor
Indicates that one entity is unfairly or abusively used by another entity as a resource, means, or advantage for the latter’s benefit.
-
C.
exploits
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
-
D.
earlyExploitationBy
Indicates that one entity takes unfair advantage of another at an early stage of their interaction, development, or process.
-
E.
эксплуатируется
Indicates that one entity is being used or operated by another, often in a way that takes advantage of its resources, capabilities, or labor.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 4:19 p.m.