Triple
T35632199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doe v. Unocal Corp. |
E1029617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transnational human rights case |
C36998
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: transnational human rights case Context triple: [Doe v. Unocal Corp., instanceOf, transnational human rights case]
-
A.
human rights case
chosen
A human rights case is a legal or quasi-legal proceeding in which an individual, group, or entity alleges that fundamental rights or freedoms protected by law have been violated, seeking recognition, remedy, or enforcement.
-
B.
international legal case
An international legal case is a formal dispute between states, international organizations, or other cross-border parties that is adjudicated or arbitrated under international law by a recognized international court, tribunal, or dispute-resolution body.
-
C.
network of national human rights institutions
A network of national human rights institutions is a coordinated system of independent, state-based bodies that collaborate to promote, protect, and strengthen human rights standards and practices domestically and internationally.
-
D.
extraterritoriality case
An extraterritoriality case is a legal dispute concerning the application or enforcement of a country's laws to persons, conduct, or events outside its territorial boundaries.
-
E.
human rights journal
A human rights journal is a periodical publication that documents, analyzes, and critiques issues, cases, and developments related to the protection and promotion of human rights.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:05 p.m.