Triple
T35632233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doe v. Unocal Corp. |
E1029617
|
entity |
| Predicate | locationOfAbuses |
P182277
|
FINISHED |
| Object | Tenasserim region of Myanmar |
E1035037
|
NE 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: Tenasserim region of Myanmar | Statement: [Doe v. Unocal Corp., locationOfAbuses, Tenasserim region of Myanmar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfAbuses Context triple: [Doe v. Unocal Corp., locationOfAbuses, Tenasserim region of Myanmar]
-
A.
percentageOfAbusesByStateForces
Indicates the proportion of total recorded abuses in a context that are attributed specifically to actions by state security or government forces.
-
B.
locationOfAttacksCondemned
Indicates that a specific location is the site of attacks that have been explicitly denounced or condemned.
-
C.
allegedMisconductLocation
chosen
Indicates the place where the alleged misconduct is reported to have occurred.
-
D.
positionOnViolence
Indicates a stance, attitude, or policy that an entity holds regarding the use, justification, or acceptability of violence.
-
E.
corruptionLocation
Indicates the place or setting where an act of corruption occurs or is centered.
- F. None of above.
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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38684ee5d88190a8d0fd33fd0f8681 |
completed | June 21, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.