Triple
T11085652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECPT |
E262112
|
entity |
| Predicate | monitoringMechanismType |
P88002
|
FINISHED |
| Object | visits to places of detention |
—
|
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: visits to places of detention | Statement: [ECPT, monitoringMechanismType, visits to places of detention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitoringMechanismType Context triple: [ECPT, monitoringMechanismType, visits to places of detention]
-
A.
supervisionMechanism
Indicates that one entity oversees, monitors, or regulates the actions or behavior of another through a defined control or guidance process.
-
B.
canBeMonitoredWith
Indicates that one entity is suitable or able to be observed, tracked, or supervised using another specified entity or method.
-
C.
monitoringApproach
chosen
Indicates the method or strategy used to observe, track, or assess a process, condition, or entity over time.
-
D.
monitoringBody
Indicates that one entity is responsible for overseeing, supervising, or tracking the activities, performance, or compliance of another entity.
-
E.
isMonitored
Indicates that an entity is being actively observed, tracked, or supervised by another entity or system.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c2c7d4819087ac793153340178 |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.