Triple
T13680523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Detention Centre, Scheveningen |
E327986
|
entity |
| Predicate | detaineesHaveRightTo |
P111129
|
FINISHED |
| Object | legal counsel |
—
|
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: legal counsel | Statement: [ICC Detention Centre, Scheveningen, detaineesHaveRightTo, legal counsel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detaineesHaveRightTo Context triple: [ICC Detention Centre, Scheveningen, detaineesHaveRightTo, legal counsel]
-
A.
detainsUnder
Indicates that one entity holds another in custody or confinement under a specific legal authority, provision, or condition.
-
B.
detainedPrisonersFrom
Indicates that an authority is holding prisoners who originate from or are associated with a specified place or source.
-
C.
hasPrisoners
Indicates that an entity holds or contains one or more individuals who are imprisoned or detained.
-
D.
inmates
Indicates that one entity is confined or held as a prisoner within an institution or facility associated with another entity.
-
E.
detainedFor
Indicates that one entity is being held in custody or confinement because of, or as a consequence of, another entity (such as a reason, charge, or event).
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66cbb088190907cb89dda8e4ebd |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.