Triple
T33634343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arundel MS 263 |
E861649
|
entity |
| Predicate | hasCodexDesignation |
—
|
GENERATED |
| Object | Codex Arundel |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodexDesignation Context triple: [Arundel MS 263, hasCodexDesignation, Codex Arundel]
-
A.
hasDiscoveryDesignation
Indicates that an entity has been assigned a specific designation or label associated with its discovery.
-
B.
hasMinorPlanetCenterDesignation
Indicates that an entity is assigned an official designation by the Minor Planet Center (e.g., for asteroids or other small Solar System bodies).
-
C.
catalogueDesignationFor
chosen
Indicates that one entity serves as the catalogue designation or identifier assigned to another entity within a cataloging system.
-
D.
hasScientificDesignation
Indicates that an entity is associated with a specific formal scientific name or designation used in scientific classification or nomenclature.
-
E.
hasPleiadesDesignation
Indicates that an astronomical object is assigned a specific designation within the Pleiades star cluster catalog.
- F. None of above.
Provenance (1 batch)
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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.