Triple
T16096537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garris Shrike |
E390496
|
entity |
| Predicate | exploitedGroup |
P699
|
FINISHED |
| Object | orphans |
—
|
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: orphans | Statement: [Garris Shrike, exploitedGroup, orphans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploitedGroup Context triple: [Garris Shrike, exploitedGroup, orphans]
-
A.
exploitedFor
Indicates that one entity is unfairly or abusively used by another entity as a resource, means, or advantage for the latter’s benefit.
-
B.
socialGroupOppressed
Indicates that the social group is subjected to systemic discrimination, marginalization, or unjust treatment by more powerful groups or institutions.
-
C.
victimGroup
chosen
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
D.
allegedTargetGroup
Indicates that a group is claimed or suspected to be the intended target of an action, plan, or attack, without confirming that the claim is true.
-
E.
victimGroupContext
Indicates the contextual circumstances or setting in which a victim group is targeted, affected, or involved in an event or action.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.