Triple
T25629187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ñuu Savi |
E642525
|
entity |
| Predicate | codicesInclude |
P46134
|
FINISHED |
| Object | Codex Nuttall |
—
|
NE NERFINISHED |
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 Nuttall | Statement: [Ñuu Savi, codicesInclude, Codex Nuttall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codicesInclude Context triple: [Ñuu Savi, codicesInclude, Codex Nuttall]
-
A.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
B.
includesFacsimilesOf
Indicates that an entity contains or provides reproductions or exact copies (facsimiles) of another entity or its content.
-
C.
sisterCodex
Indicates a sibling relationship where one codex or text is considered a sister counterpart to another, typically implying close similarity, shared origin, or parallel status.
-
D.
foundInCodexWith
chosen
Indicates that one entity is documented together with another entity within the same codex or manuscript.
-
E.
textsIncludedIn
Indicates that certain texts are contained within, or form a subset of, a larger collection or body of texts.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa260734819080d7d32c6912d267 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:16 p.m.