Triple
T4885896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New General Catalogue |
E109437
|
entity |
| Predicate | laterFormats |
P50239
|
FINISHED |
| Object | digital database |
—
|
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: digital database | Statement: [New General Catalogue, laterFormats, digital database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterFormats Context triple: [New General Catalogue, laterFormats, digital database]
-
A.
relatedFormat
Indicates that two resources are available in different but closely related formats or media representations of essentially the same content.
-
B.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
D.
subsequentReleaseFormat
chosen
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
E.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:28 p.m.