Triple
T4680817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Geneva Convention of 1906 |
E103795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law of armed conflict instrument |
C1702
|
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: law of armed conflict instrument Context triple: [Second Geneva Convention of 1906, instanceOf, law of armed conflict instrument]
-
A.
international humanitarian law instrument
chosen
An international humanitarian law instrument is a formal legal document, such as a treaty, convention, or protocol, that establishes rules governing the conduct of parties during armed conflict to protect persons who are not or are no longer participating in hostilities.
-
B.
military legal code
A military legal code is a formal system of laws and regulations that governs the conduct, discipline, rights, and obligations of members of the armed forces.
-
C.
international human rights instrument
An international human rights instrument is a formal, legally or politically binding document adopted by states or international organizations that defines, codifies, and promotes the protection of fundamental human rights and freedoms across national borders.
-
D.
administrative instrument
An administrative instrument is a formal tool, document, or mechanism used by an organization or authority to implement, manage, or regulate administrative processes and decisions.
-
E.
military regulations
Military regulations are formal, authoritative rules and directives that govern the conduct, organization, procedures, and responsibilities of armed forces personnel and operations.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:16 p.m.