Triple
T23568490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hob. XXI:3 |
E580034
|
entity |
| Predicate | usedInCataloguing |
P137032
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hob. XXI:3, usedInCataloguing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCataloguing Context triple: [Hob. XXI:3, usedInCataloguing, yes]
-
A.
usedInCatalogue
Indicates that something is included or referenced as an entry within a catalogue.
-
B.
cataloguingStandard
chosen
Indicates the cataloguing rules or standard under which an item’s descriptive and access information has been created or recorded.
-
C.
usedInLibrary
Indicates that something is utilized or applied within the context of a library, such as a software library or a physical library system.
-
D.
catalogued as
Indicates that one entity has been recorded or registered under a specific identifier or entry within a catalog or systematic listing.
-
E.
usedInLabeling
Indicates that something is employed or applied as part of a labeling process or activity.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6e11008190bdd28c3f85e3004e |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:35 p.m.