Triple
T36684169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Part |
E905770
|
entity |
| Predicate | partOfLegalCode |
P57899
|
FINISHED |
| Object | Siete 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: Siete Partidas | Statement: [Third Part, partOfLegalCode, Siete Partidas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLegalCode Context triple: [Third Part, partOfLegalCode, Siete Partidas]
-
A.
legalBasisInPart
Indicates that something is justified, authorized, or supported only partially by a specified legal basis or provision.
-
B.
partOfLegalSystem
chosen
Indicates that something belongs to, is included within, or functions as a component of a particular legal system.
-
C.
legalCodePreceded
Indicates that one legal code existed or was in force before another legal code in a temporal or historical sequence.
-
D.
legalCodeRecordedIn
Indicates that a legal code is documented, registered, or officially stored within a particular record, system, or repository.
-
E.
deJurePartOf
Indicates that one entity is legally or formally recognized as a constituent part or subdivision of another entity, according to official rules or law.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0124a5d7848190a6b56d18db2f661d |
completed | May 11, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_6a01243da1808190ada3ce553e3f55b6 |
completed | May 11, 2026, 12:35 a.m. |
Created at: May 3, 2026, 4:12 p.m.