Triple
T30307396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Date clan |
E770821
|
entity |
| Predicate | famousLeader |
P116364
|
FINISHED |
| Object | Date Masamune |
—
|
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: Date Masamune | Statement: [Date clan, famousLeader, Date Masamune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousLeader Context triple: [Date clan, famousLeader, Date Masamune]
-
A.
notableHistoricalLeaders
chosen
Indicates that the related entities are recognized as historically significant leaders, such as rulers, commanders, or influential figures in major historical events.
-
B.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
C.
militaryLeader
Indicates that one entity serves as the commanding military leader of another entity, such as a state, organization, or armed force.
-
D.
notableHistoricalEntity
Indicates that an entity holds recognized historical significance or prominence within a historical context.
-
E.
foundingLeaderOf
Indicates that an entity is the primary founder who established and initially led another entity, such as an organization, movement, or institution.
- 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_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_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:49 p.m.