Triple
T29799581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedric the Saxon |
E756654
|
entity |
| Predicate | permitsMarriageOf |
P110081
|
FINISHED |
| Object | Rowena and Wilfred of Ivanhoe |
—
|
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: Rowena and Wilfred of Ivanhoe | Statement: [Cedric the Saxon, permitsMarriageOf, Rowena and Wilfred of Ivanhoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitsMarriageOf Context triple: [Cedric the Saxon, permitsMarriageOf, Rowena and Wilfred of Ivanhoe]
-
A.
marriageRestriction
Indicates a legal or social limitation on who or under what conditions individuals are allowed to marry.
-
B.
supportsMarriageBetween
chosen
Indicates that one entity endorses or is in favor of a marital union between the specified parties.
-
C.
acceptsMarriageTo
Indicates that one entity formally agrees to enter into a marriage with another entity.
-
D.
regardsMarriageAs
Indicates that one entity holds a particular view, attitude, or evaluative stance toward the institution or concept of marriage.
-
E.
marriesFor
Indicates that one entity enters into marriage with another entity specifically for a particular reason, motive, or benefit.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67525c9a0819084e47299fa5dabfe |
completed | May 2, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:17 p.m.