Triple
T37304558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wq 48 |
E926041
|
entity |
| Predicate | hasNumberInCatalogue |
P192713
|
FINISHED |
| Object | 48 |
—
|
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: 48 | Statement: [Wq 48, hasNumberInCatalogue, 48]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberInCatalogue Context triple: [Wq 48, hasNumberInCatalogue, 48]
-
A.
hasCatalogNumberSystem
Indicates that an entity uses or is associated with a particular catalog numbering system for organizing or identifying items.
-
B.
hasOrdinalInCatalogue
chosen
Indicates that an entity is assigned a specific ordinal position or sequence number within a catalogue.
-
C.
hasCatalogueNumberInDeutschCatalogue
Indicates that an entity is assigned a specific catalogue number within the Deutsch catalogue classification system.
-
D.
hasPartNumber
Indicates that one entity is assigned or associated with a specific part number used to identify it within a catalog, system, or inventory.
-
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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 3, 2026, 4:16 p.m.