Triple
T36186536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnamagnæan Manuscript Collection |
E1046861
|
entity |
| Predicate | containsItemType |
P70092
|
FINISHED |
| Object | codices |
—
|
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: codices | Statement: [Arnamagnæan Manuscript Collection, containsItemType, codices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsItemType Context triple: [Arnamagnæan Manuscript Collection, containsItemType, codices]
-
A.
hasCollectionItemBy
Indicates that an entity possesses or includes a specific item as part of its collection, identified or referenced by some key or identifier.
-
B.
containsCategory
chosen
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
-
C.
containsFurnitureBy
Indicates that one entity includes or holds furniture items that are provided, created, or specified by another entity.
-
D.
hasInGameItemType
Indicates that an entity possesses or is associated with a specific type or category of in-game item.
-
E.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a011e5a419081908d06a07b395ebd97 |
completed | May 11, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_6a011de119048190b27d361cffabc228 |
completed | May 11, 2026, 12:08 a.m. |
Created at: May 3, 2026, 4:08 p.m.