Triple
T32368456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianyou |
E827062
|
entity |
| Predicate | eraIntroducedBy |
P173982
|
FINISHED |
| Object | Emperor Zhaozong of Tang |
—
|
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: Emperor Zhaozong of Tang | Statement: [Tianyou, eraIntroducedBy, Emperor Zhaozong of Tang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraIntroducedBy Context triple: [Tianyou, eraIntroducedBy, Emperor Zhaozong of Tang]
-
A.
wereIntroducedBy
Indicates that one entity became known, presented, or brought to the attention of another entity through the action or mediation of a third party.
-
B.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
C.
cultIntroducedBy
Indicates that a particular cult or religious practice was brought into a place, group, or culture through the agency or influence of a specific person or entity.
-
D.
oftenIntroducedBy
Indicates that one entity is frequently presented, mentioned, or brought into context by another entity.
-
E.
termIntroducedBy
Indicates that a specific term was first presented, defined, or brought into use by a particular source or agent.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be9f57048190819d133d4caba58e |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:50 a.m.