Triple
T31069990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoboken catalogue |
E791790
|
entity |
| Predicate | usedAsCatalogueNumberPrefix |
P93740
|
FINISHED |
| Object | Hob. |
—
|
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: Hob. | Statement: [Hoboken catalogue, usedAsCatalogueNumberPrefix, Hob.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCatalogueNumberPrefix Context triple: [Hoboken catalogue, usedAsCatalogueNumberPrefix, Hob.]
-
A.
hasCatalogNumberPrefix
Indicates that an item’s catalog number begins with a specified prefix.
-
B.
usedAsPrefixIn
chosen
Indicates that one element functions as a leading prefix component in the formation or representation of another element.
-
C.
originalCatalogNumberFor
Indicates that one resource is the original catalog number assigned to another resource.
-
D.
alternativeCatalogNumber
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
-
E.
cataloguePrefix
Indicates that one entity serves as the initial or leading segment of another entity’s catalogue identifier or listing code.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 29, 2026, 9:01 p.m.