Triple
T15949614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De la Garza family ranch |
E386778
|
entity |
| Predicate | keyEvents |
P83350
|
FINISHED |
| Object | Tita’s birth |
—
|
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: Tita’s birth | Statement: [De la Garza family ranch, keyEvents, Tita’s birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyEvents Context triple: [De la Garza family ranch, keyEvents, Tita’s birth]
-
A.
keyEventDescribed
Indicates that a key or significant event is explicitly described or detailed in relation to an entity or context.
-
B.
keyEventInRise
Indicates that a key event occurs during or contributes to the rise or escalation phase of a process, situation, or storyline.
-
C.
keyAction
Indicates an action that is performed using a key, typically involving locking, unlocking, or otherwise operating a mechanism that requires a key.
-
D.
mainEvents
chosen
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
-
E.
keyReport
Indicates that an entity serves as a primary or central report associated with another entity, such as a main document summarizing key information or findings.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.