Triple
T24688421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid Codex |
E611360
|
entity |
| Predicate | numberOfFolds |
P159029
|
FINISHED |
| Object | approximately 56 |
—
|
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: approximately 56 | Statement: [Madrid Codex, numberOfFolds, approximately 56]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfFolds Context triple: [Madrid Codex, numberOfFolds, approximately 56]
-
A.
canFold
Indicates that one entity has the ability to be bent or collapsed into a more compact form, typically without breaking.
-
B.
foldingType
Indicates the specific manner or configuration in which something is folded or arranged into a folded form.
-
C.
folding
Indicates that one entity bends or doubles another entity (or itself) so that parts of it lie flat against or over each other.
-
D.
folded
Indicates that an entity has been bent or doubled over onto itself, typically along a line or crease, changing its original flat or extended form.
-
E.
foldedYear
Indicates that one entity represents a year that has been combined, aggregated, or "folded" into another temporal grouping or representation.
- F. None of above. chosen
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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 18, 2026, 3:19 a.m.