Triple
T23244566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSV 1589 |
E581548
|
entity |
| Predicate | hasNumberInCatalog |
P66286
|
FINISHED |
| Object | 1589 |
—
|
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: 1589 | Statement: [NSV 1589, hasNumberInCatalog, 1589]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberInCatalog Context triple: [NSV 1589, hasNumberInCatalog, 1589]
-
A.
hasPartNumber
chosen
Indicates that one entity is assigned or associated with a specific part number used to identify it within a catalog, system, or inventory.
-
B.
hasNumberCategory
Indicates that an entity is associated with a specific numerical classification or type.
-
C.
hasCatalogNumberPrefix
Indicates that an item’s catalog number begins with a specified prefix.
-
D.
hasOnlineCatalog
Indicates that an entity provides a catalog of its items or offerings that is accessible via the internet.
-
E.
discoveredInCatalogue
Indicates that an entity was identified or first recognized through information found in a specific 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.