Triple
T30725779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hob.I:45 |
E782275
|
entity |
| Predicate | hasOrdinalInCatalogue |
P192713
|
FINISHED |
| Object | 45 |
—
|
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: 45 | Statement: [Hob.I:45, hasOrdinalInCatalogue, 45]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrdinalInCatalogue Context triple: [Hob.I:45, hasOrdinalInCatalogue, 45]
-
A.
hasOrdinalSeries
Indicates that one entity belongs to, or is positioned within, an ordered sequence or series relative to other entities.
-
B.
hasOrdinalTitle
Indicates that an entity holds a title or designation that includes an ordinal position (e.g., first, second, third) within a sequence or hierarchy.
-
C.
belongsToCatalogOf
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
D.
discoveredInCatalogue
Indicates that an entity was identified or first recognized through information found in a specific catalogue.
-
E.
baseOrdinal
Indicates that one entity serves as the reference or starting point for ordering another entity within an ordered sequence.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
| PDg | Predicate description generation | batch_69fd28379d2c8190903ba228ee1cc756 |
completed | May 8, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:36 p.m.