Triple
T3613766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Treaty Series, volume 78 |
E76549
|
entity |
| Predicate | seriesNumbering |
P3378
|
FINISHED |
| Object | volume 78 |
—
|
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: volume 78 | Statement: [United Nations Treaty Series, volume 78, seriesNumbering, volume 78]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesNumbering Context triple: [United Nations Treaty Series, volume 78, seriesNumbering, volume 78]
-
A.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
B.
serviceNumbering
Indicates that a specific service is assigned or associated with a particular identifying number or code.
-
C.
serialNumber
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
-
D.
numberingType
chosen
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
E.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc279f6948190b9655a4cf3e77d89 |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.