Triple
T31365117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzong |
E799986
|
entity |
| Predicate | ascendedThroneAt |
P114331
|
FINISHED |
| Object | Lingwu |
—
|
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: Lingwu | Statement: [Suzong, ascendedThroneAt, Lingwu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ascendedThroneAt Context triple: [Suzong, ascendedThroneAt, Lingwu]
-
A.
ascendedThroneYear
Indicates the year in which a person formally ascended to or took possession of a throne or ruling position.
-
B.
ascendedThroneDuring
Indicates that a person became the ruling monarch at some point within a specified time period or event.
-
C.
ascendedThroneIn
chosen
Indicates that a person assumed or was elevated to a throne or ruling position in a specified place or jurisdiction.
-
D.
ascendedToThroneIn
Indicates the time or place at which a person formally became the ruling monarch or assumed the throne.
-
E.
ascendedToThroneAs
Indicates that an individual assumed royal power and officially became the reigning monarch under a specific title or role.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f846cb8819086c0f2722c1e1714 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:18 p.m.