Triple
T5094220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowell Codex |
E114826
|
entity |
| Predicate | folioFormat |
P130
|
FINISHED |
| Object | codex |
—
|
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: codex | Statement: [Nowell Codex, folioFormat, codex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: folioFormat Context triple: [Nowell Codex, folioFormat, codex]
-
A.
folio
Indicates that one entity is a specific page, leaf, or numbered side within a larger bound or paginated document associated with another entity.
-
B.
portfolioOf
Indicates that one entity is the collection of investments, works, or assets that are owned, managed, or represented by another entity.
-
C.
typicalPortfolio
Indicates that one entity is the standard or representative portfolio associated with another entity (such as a person, account, or organization).
-
D.
portfolioHolderTitle
Indicates the formal title or designation held by the person or entity that owns or manages the portfolio.
-
E.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75454920819086e09d6055087e40 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.