Triple
T33264437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nero D IV |
E851606
|
entity |
| Predicate | hasCatalogueEntryIn |
P19933
|
FINISHED |
| Object | British Library online catalogue |
—
|
NE NERFINISHED |
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: British Library online catalogue | Statement: [Nero D IV, hasCatalogueEntryIn, British Library online catalogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogueEntryIn Context triple: [Nero D IV, hasCatalogueEntryIn, British Library online catalogue]
-
A.
belongsToCatalogOf
chosen
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
B.
hasEntryOn
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
C.
hasCatalogueContext
Indicates that something is associated with, or occurs within, a specific catalogue-related context or framework.
-
D.
hasCatalogView
Indicates that an entity is associated with a particular way or mode of viewing or presenting a catalog.
-
E.
hasOrdinalInCatalogue
Indicates that an entity is assigned a specific ordinal position or sequence number within a catalogue.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 1, 2026, 1:32 a.m.