Triple
T25083297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casilda |
E628242
|
entity |
| Predicate | secretlyBetrothedTo |
P142151
|
FINISHED |
| Object | missing heir to the throne of Barataria |
—
|
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: missing heir to the throne of Barataria | Statement: [Casilda, secretlyBetrothedTo, missing heir to the throne of Barataria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretlyBetrothedTo Context triple: [Casilda, secretlyBetrothedTo, missing heir to the throne of Barataria]
-
A.
secretlyEngagedTo
chosen
Indicates that one person is engaged to marry another, but this engagement is intentionally kept hidden from others.
-
B.
hasSecretMarriageWith
Indicates a relationship where two entities are secretly married to each other, with the marriage intentionally concealed from others.
-
C.
betrothedByFatherTo
Indicates that an individual is formally promised or given in marriage to another person by their father’s decision or arrangement.
-
D.
isFianceeOf
Indicates that one person is the engaged-to-be-married partner of another person.
-
E.
hasConcubineFrom
Indicates that a person has a concubine whose origin or affiliation is from a specified place or source.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f461e18c288190a0d06a7756fed024 |
completed | May 1, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:22 a.m.