Triple
T37008794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seventh Partida |
E915882
|
entity |
| Predicate | isPartOfCanonicalNumber |
P201518
|
FINISHED |
| Object | seven Partidas |
—
|
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: seven Partidas | Statement: [Seventh Partida, isPartOfCanonicalNumber, seven Partidas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCanonicalNumber Context triple: [Seventh Partida, isPartOfCanonicalNumber, seven Partidas]
-
A.
hasCanonicalNumber
Indicates that an entity is associated with its officially recognized or standard reference number.
-
B.
isCanonical
Indicates that something represents the standard, authoritative, or officially accepted form within a given context or system.
-
C.
hasPartInCanonization
Indicates that an entity participated in or contributed to the process of canonization of another entity.
-
D.
numericPartRepresents
Indicates that a numeric component of something stands for or encodes a specific value, property, or aspect of that thing.
-
E.
isClassicNumber
Indicates that a number belongs to a traditionally recognized or canonical set of numbers defined as "classic" within a given context.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69ffff2533248190ac291f5f2e858320 |
completed | May 10, 2026, 3:44 a.m. |
Created at: May 3, 2026, 4:14 p.m.