Triple
T38044043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atsumori |
E949565
|
entity |
| Predicate | hasWakiRole |
P189566
|
FINISHED |
| Object | Renshō (Kumagai Naozane as monk) |
—
|
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: Renshō (Kumagai Naozane as monk) | Statement: [Atsumori, hasWakiRole, Renshō (Kumagai Naozane as monk)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWakiRole Context triple: [Atsumori, hasWakiRole, Renshō (Kumagai Naozane as monk)]
-
A.
wakiRole
chosen
Indicates that an entity serves as the waki, or supporting/secondary role, in a Noh drama performance or similar structured interaction.
-
B.
hasWaka
Indicates that an entity possesses, contains, or is associated with a waka (such as a traditional canoe, vessel, or similarly defined object).
-
C.
hasWingRole
Indicates that an entity holds a specific role or position within a wing or sub-unit of a larger organization or structure.
-
D.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
E.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:20 p.m.