Triple
T18541269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGC 5336 |
E453103
|
entity |
| Predicate | catalogNumberDDO |
P132083
|
FINISHED |
| Object | 66 |
—
|
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: 66 | Statement: [UGC 5336, catalogNumberDDO, 66]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogNumberDDO Context triple: [UGC 5336, catalogNumberDDO, 66]
-
A.
workCatalogueNumber
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
B.
alternativeCatalogNumber
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
-
C.
holotypeSpecimenNumber
Indicates the identifying specimen number assigned to the holotype that formally defines a taxon in biological classification.
-
D.
museumInventoryNumber
Indicates the unique catalog or inventory identifier assigned to an item within a museum’s collection.
-
E.
catalogueRaisonneNumber
Indicates the identifier assigned to a work in a catalogue raisonné, linking it to its authoritative scholarly listing.
- F. None of above. chosen
Provenance (4 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b749b88190ad03b26bee3c89df |
completed | April 19, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.