Triple
T29901401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Depositary Notifications (CN series) |
E759415
|
entity |
| Predicate | hasSeriesCode |
P145090
|
FINISHED |
| Object | CN |
—
|
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: CN | Statement: [Depositary Notifications (CN series), hasSeriesCode, CN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeriesCode Context triple: [Depositary Notifications (CN series), hasSeriesCode, CN]
-
A.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
B.
hasStandardSeries
Indicates that an entity is associated with, or belongs to, a designated standard series or standardized sequence.
-
C.
hasSeriesRecord
Indicates that one entity maintains a documented record or history of another entity’s participation or performance within a series.
-
D.
seriesCode
chosen
Indicates that an entity is assigned a specific code identifying the series or collection to which it belongs.
-
E.
hasSeriesStructure
Indicates that one entity is organized as a sequence or series of related components or parts.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 29, 2026, 6:06 p.m.