Triple
T15432232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ley de Enjuiciamiento Civil |
E369667
|
entity |
| Predicate | esComplementadaPor |
P55853
|
FINISHED |
| Object | Constitución Española |
—
|
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: Constitución Española | Statement: [Ley de Enjuiciamiento Civil, esComplementadaPor, Constitución Española]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: esComplementadaPor Context triple: [Ley de Enjuiciamiento Civil, esComplementadaPor, Constitución Española]
-
A.
laterComplementedBy
chosen
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later entity.
-
B.
relatesComplementTo
Indicates that one entity serves as a complement or completing counterpart to another entity within a specified context or structure.
-
C.
requiresComplement
Indicates that one entity depends on another entity as a necessary complement to be complete, functional, or valid.
-
D.
complement
Indicates that one entity completes, enhances, or makes another entity whole or more effective by providing what it lacks.
-
E.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03eda01cc8190843e23b260b8503c |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.