Triple
T35173521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Frederick Charles of Hesse |
E1015621
|
entity |
| Predicate | regnalNameProposed |
P84567
|
FINISHED |
| Object | Väinö I |
—
|
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: Väinö I | Statement: [Prince Frederick Charles of Hesse, regnalNameProposed, Väinö I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regnalNameProposed Context triple: [Prince Frederick Charles of Hesse, regnalNameProposed, Väinö I]
-
A.
nameProposedBy
Indicates that one entity is the proposer or originator of a particular name assigned to another entity.
-
B.
nameProposedIn
Indicates that a particular name was suggested or put forward within a specific proposal, context, or event.
-
C.
regnalNameAsPretender
chosen
Indicates the name a person uses as a claimed ruler or monarch while not officially recognized as holding that throne.
-
D.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
E.
proposedStateName
Indicates that one entity has suggested or put forward a particular name to be used as the state name for another entity.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d72dd8c8190bf6fb58d45e4c4a1 |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.