Triple
T25676574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nōhime |
E643821
|
entity |
| Predicate | spouseDomain |
P96915
|
FINISHED |
| Object | Owari Province |
—
|
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: Owari Province | Statement: [Nōhime, spouseDomain, Owari Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseDomain Context triple: [Nōhime, spouseDomain, Owari Province]
-
A.
spouseRealm
chosen
Indicates that two entities are spouses within, or in relation to, a particular realm, jurisdiction, or domain.
-
B.
spouseOfWork
Indicates that one person is the spouse of another specifically in the context of their workplace or professional environment.
-
C.
spouseService
Indicates that one person provides a service or assistance specifically for their spouse within the context of a relationship or arrangement.
-
D.
spouseMember
Indicates that one entity is the spouse (married partner) of another entity.
-
E.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
- 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_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 21, 2026, 7:39 p.m.