Triple
T30307398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Date clan |
E770821
|
entity |
| Predicate | MasamuneRole |
P169392
|
FINISHED |
| Object | founder of Sendai Domain |
—
|
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: founder of Sendai Domain | Statement: [Date clan, MasamuneRole, founder of Sendai Domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MasamuneRole Context triple: [Date clan, MasamuneRole, founder of Sendai Domain]
-
A.
MasamuneTitle
Indicates that one entity holds the specific title or designation known as "Masamune" in relation to another entity.
-
B.
swordsman
Indicates that an entity is a person who practices or is skilled in the use of swords.
-
C.
roleInShinKokinWakashu
Indicates the specific role or involvement an entity has in relation to the Shin Kokin Wakashū (e.g., as compiler, editor, or contributor).
-
D.
roleInMonsterVerse
Indicates that an entity has a specific role or function within the MonsterVerse franchise or universe.
-
E.
roleInBladeTrinity
Indicates that an entity participated in the movie "Blade: Trinity" in a specific role (such as actor, director, or crew position).
- F. None of above. chosen
Provenance (4 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6816966e8819094d81abb060be372 |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:49 p.m.