Triple
T30654674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ley del Matrimonio Civil |
E780352
|
entity |
| Predicate | contexto histórico |
P43371
|
FINISHED |
| Object | siglo XIX en México |
—
|
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: siglo XIX en México | Statement: [Ley del Matrimonio Civil, contexto histórico, siglo XIX en México]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contexto histórico Context triple: [Ley del Matrimonio Civil, contexto histórico, siglo XIX en México]
-
A.
hasHistoricalContext
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
B.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
C.
historicalBackground
chosen
Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
-
D.
shareHistoricalContextAs
Indicates that two or more entities are associated with or understood within the same historical background, period, or circumstances.
-
E.
historicalCondition
Indicates that one entity represents a condition, state, or circumstance that applied to another entity at some point in the past.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:30 p.m.