Triple
T2001177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subcommittee on Prevention of Torture |
E43473
|
entity |
| Predicate | hasWorkingMethods |
P33646
|
FINISHED |
| Object | confidential visits |
—
|
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: confidential visits | Statement: [Subcommittee on Prevention of Torture, hasWorkingMethods, confidential visits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkingMethods Context triple: [Subcommittee on Prevention of Torture, hasWorkingMethods, confidential visits]
-
A.
hasWorkingMethod
Indicates that one entity possesses or employs a functional method, procedure, or technique to achieve a particular task or outcome.
-
B.
hasWorkingBody
Indicates that an entity possesses a functional, operational physical body.
-
C.
hasWorkingMode
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
D.
usesMethods
chosen
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
E.
hasWorkContext
Indicates that an entity is associated with a particular work-related situation, environment, or context in which it is relevant or applies.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb880c710819098fb877052ce56dc |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.