Triple
T34810360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLM in International Law |
E1003482
|
entity |
| Predicate | commonModules |
P197939
|
FINISHED |
| Object | international human rights law |
—
|
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: international human rights law | Statement: [LLM in International Law, commonModules, international human rights law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonModules Context triple: [LLM in International Law, commonModules, international human rights law]
-
A.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
-
B.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
C.
commonApplication
Indicates that multiple entities share or participate in the same application, process, or usage context.
-
D.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
E.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69feba0e362c81909883a3f24a4a9545 |
completed | May 9, 2026, 4:37 a.m. |
Created at: May 3, 2026, 3:59 p.m.