Triple
T38069688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morg |
E950560
|
entity |
| Predicate | predecessorAsHerald |
P197153
|
FINISHED |
| Object | Nova (Frankie Raye) |
—
|
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: Nova (Frankie Raye) | Statement: [Morg, predecessorAsHerald, Nova (Frankie Raye)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsHerald Context triple: [Morg, predecessorAsHerald, Nova (Frankie Raye)]
-
A.
predecessorAsHeir
Indicates that one entity previously held the status of heir before being succeeded by another in that role.
-
B.
predecessorMonogram
Indicates that one monogram directly precedes another in a defined sequence or order.
-
C.
predecessorInRegency
Indicates that one regent directly preceded another in holding regency authority over the same domain or office.
-
D.
predecessorAsHeirApparent
Indicates that one entity previously held the position of heir apparent to another entity (such as a throne, title, or office) before being succeeded in that role.
-
E.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
| PDg | Predicate description generation | batch_69fe78e35e6c8190b8b440777912f64e |
completed | May 8, 2026, 11:59 p.m. |
Created at: May 3, 2026, 4:21 p.m.