Triple
T32572975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Zhuangxiang of Qin |
E832564
|
entity |
| Predicate | nobleTitleBeforeKingship |
P123375
|
FINISHED |
| Object | Prince of Qin |
—
|
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: Prince of Qin | Statement: [King Zhuangxiang of Qin, nobleTitleBeforeKingship, Prince of Qin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleBeforeKingship Context triple: [King Zhuangxiang of Qin, nobleTitleBeforeKingship, Prince of Qin]
-
A.
nobleTitleElevated
Indicates that an entity’s noble rank or title has been raised to a higher level of nobility.
-
B.
nobleTitleHeirTo
Indicates that one entity is the designated heir to the noble title held by another entity.
-
C.
nobleTitleOrStatus
chosen
Indicates that one entity holds, claims, or is associated with a particular noble rank, title, or social status in relation to another entity.
-
D.
traditionalTitleOfKing
Indicates that the object is the customary or historically recognized royal title held by the king specified as the subject.
-
E.
nobleTitleFrom
Indicates that a person derives or holds their noble title from a specified source, such as a place, lineage, or authority.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:04 a.m.