Triple
T30742186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Linzi |
E782720
|
entity |
| Predicate | associatedDynasticEra |
P145875
|
FINISHED |
| Object | Tang dynasty |
E34804
|
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: Tang dynasty | Statement: [Prince of Linzi, associatedDynasticEra, Tang dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDynasticEra Context triple: [Prince of Linzi, associatedDynasticEra, Tang dynasty]
-
A.
dynasticEraName
Indicates the named historical period or era associated with a particular dynasty’s rule.
-
B.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
-
C.
dynasticPhases
Indicates the successive ruling periods or stages within a dynasty’s history.
-
D.
belongsToDynasticHistory
chosen
Indicates that something is part of, or associated with, a particular dynastic historical period or lineage.
-
E.
prominentDynasty
Indicates that a dynasty holds significant historical, political, or cultural importance relative to other dynasties.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28991a80b0819093e4d63fabe3e5f1 |
completed | June 9, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:38 p.m.