Triple
T38394965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godunoff |
E900730
|
entity |
| Predicate | notableInHistoryThrough |
P140627
|
FINISHED |
| Object | Boris Godunov |
E48836
|
NE 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: Boris Godunov | Statement: [Godunoff, notableInHistoryThrough, Boris Godunov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInHistoryThrough Context triple: [Godunoff, notableInHistoryThrough, Boris Godunov]
-
A.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
B.
hasHistoricalSignificanceThrough
chosen
Indicates that one entity possesses historical importance or relevance by means of, or as established through, its connection or association with another entity or event.
-
C.
knownInHistoryAs
Indicates that an entity is recognized or referred to by a particular name or title in historical records or accounts.
-
D.
historicalPeople
Indicates that the related entities are people who lived in or are associated with a past historical period or context.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- F. None of above.
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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41d63e4214819084453df734df02e2 |
completed | June 29, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.