Triple
T16269910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Contracting Parties |
E394970
|
entity |
| Predicate | areRecordedBy |
P122453
|
FINISHED |
| Object | treaty depositary |
—
|
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: treaty depositary | Statement: [High Contracting Parties, areRecordedBy, treaty depositary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areRecordedBy Context triple: [High Contracting Parties, areRecordedBy, treaty depositary]
-
A.
mainlyRecordedBy
Indicates that the primary or most significant recording of something (such as a work, event, or data set) was made by a particular agent or entity.
-
B.
alsoRecordedBy
Indicates that the same work, event, or material has been additionally recorded by another recorder or recording entity.
-
C.
isOftenRecordedWith
Indicates that one entity is frequently documented, captured, or logged at the same time as another entity.
-
D.
laterRecordedBy
Indicates that the subject work or version was recorded at a later time by the specified artist or entity.
-
E.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24608dd20819082f46a64af233038 |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.