Triple
T27766642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qinglong |
E701617
|
entity |
| Predicate | usedUnderEmperor |
P9805
|
FINISHED |
| Object | Cao Rui |
—
|
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: Cao Rui | Statement: [Qinglong, usedUnderEmperor, Cao Rui]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedUnderEmperor Context triple: [Qinglong, usedUnderEmperor, Cao Rui]
-
A.
formedUnderEmperor
Indicates that an entity (such as a group, institution, or administrative unit) was created or established during the reign or authority of a specific emperor.
-
B.
underRomanEmperor
Indicates that one entity existed, occurred, or was governed during the reign of the specified Roman emperor.
-
C.
concludedUnderEmperor
Indicates that an event, agreement, or process was completed or formally concluded during the reign of a specific emperor.
-
D.
associatedWithEmperor
Indicates a relationship in which an entity has a connection, link, or affiliation with an emperor, such as through service, influence, kinship, or shared authority.
-
E.
hasDateUnderEmperor
chosen
Indicates that an event or record occurred during the reign of a specified emperor.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637939be0819082653d4115cd1be1 |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:31 p.m.