Triple
T33634343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arundel MS 263 |
E861649
|
entity |
| Predicate | hasCodexDesignation |
P182517
|
FINISHED |
| Object | Codex Arundel |
E245129
|
NE 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: Codex Arundel | Statement: [Arundel MS 263, hasCodexDesignation, Codex Arundel]
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 (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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3611b1ecd481908341266508748de1 |
completed | June 20, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:41 a.m.