Triple
T20352272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGC |
E496041
|
entity |
| Predicate | hasCatalogNumberingScheme |
P37553
|
FINISHED |
| Object | UGC number |
—
|
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: UGC number | Statement: [UGC, hasCatalogNumberingScheme, UGC number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogNumberingScheme Context triple: [UGC, hasCatalogNumberingScheme, UGC number]
-
A.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
-
B.
hasCabinetNumberingSystem
Indicates that there is a specific scheme or method used to assign and organize identification numbers to cabinets.
-
C.
historicalNumberingScheme
Indicates that the associated numbering system or identifier reflects a past or legacy scheme that was used historically rather than the current one.
-
D.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
E.
usesHarmonizedNumberingWith
Indicates that two entities apply the same standardized numbering scheme so their identifiers or codes are directly comparable or aligned.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67850ace48190b19aff5780fef7e8 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.