Triple
T5514385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Chambers |
E144644
|
entity |
| Predicate | mayBeRequestedBy |
P20806
|
FINISHED |
| Object | parties to a dispute |
—
|
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: parties to a dispute | Statement: [Special Chambers, mayBeRequestedBy, parties to a dispute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeRequestedBy Context triple: [Special Chambers, mayBeRequestedBy, parties to a dispute]
-
A.
mayRequest
chosen
Indicates that one entity is permitted or authorized to make a request to another entity or for a particular resource or action.
-
B.
requestedBy
Indicates that one entity has made a request for something to be done, provided, or obtained by another entity.
-
C.
mayBeFilledBy
Indicates that one entity has the potential or permission to be occupied, completed, or satisfied by another entity.
-
D.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
E.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f5b4e988190b590b4157cf089c1 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.