Triple
T25676585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nōhime |
E643821
|
entity |
| Predicate | marriageArrangedFor |
P53943
|
FINISHED |
| Object | peace between Mino and Owari |
—
|
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: peace between Mino and Owari | Statement: [Nōhime, marriageArrangedFor, peace between Mino and Owari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageArrangedFor Context triple: [Nōhime, marriageArrangedFor, peace between Mino and Owari]
-
A.
arrangedMarriageFor
chosen
Indicates that one entity has organized or set up a marriage for another entity.
-
B.
seeksToArrangeMarriageFor
Indicates an entity’s intention or effort to organize or facilitate a marriage for another entity.
-
C.
marriesFor
Indicates that one entity enters into marriage with another entity specifically for a particular reason, motive, or benefit.
-
D.
destinedToMarry
Indicates that two entities are fated or predetermined to marry each other in the future.
-
E.
marriageResolvedBy
Indicates that a marital relationship between two parties has been formally concluded or dissolved through a specific resolving action or process (e.g., divorce, annulment).
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 7:39 p.m.