Triple
T17694294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex 150 |
E441120
|
entity |
| Predicate | isPartOfCollectionType |
P1925
|
FINISHED |
| Object | medieval manuscripts collection |
—
|
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: medieval manuscripts collection | Statement: [Codex 150, isPartOfCollectionType, medieval manuscripts collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCollectionType Context triple: [Codex 150, isPartOfCollectionType, medieval manuscripts collection]
-
A.
isCollectionOf
Indicates that one entity is a group or aggregate composed of multiple instances or elements of another entity.
-
B.
isCollection
Indicates that an entity functions as a collection that groups or aggregates multiple items or elements.
-
C.
partOfCollection
chosen
Indicates that an entity belongs to, or is included within, a larger collection or set.
-
D.
hasCollectionType
Indicates that an entity is associated with or organized under a specific type or category of collection.
-
E.
isPartOfType
Indicates that one type or category is a constituent or subset within a larger, encompassing type or category.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715485d88190b9b6f347ff85d7c7 |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:04 a.m.