Triple
T8202597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tang of Shang |
E191613
|
entity |
| Predicate | ancestralTitle |
P914
|
FINISHED |
| Object | First Ancestor of Shang |
—
|
LITERAL 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: First Ancestor of Shang | Statement: [Tang of Shang, ancestralTitle, First Ancestor of Shang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralTitle Context triple: [Tang of Shang, ancestralTitle, First Ancestor of Shang]
-
A.
aristocraticTitleIn
Indicates that an entity holds or is associated with a specific aristocratic or noble title within a particular jurisdiction or context.
-
B.
aristocraticTitleHeldFrom
Indicates the time period or starting point from which an aristocratic title was held by an entity.
-
C.
associatedNobleTitle
chosen
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
D.
aristocraticTitleHeldTo
Indicates that one entity holds or bears an aristocratic or noble title in relation to another entity (such as a person, family, or jurisdiction).
-
E.
royalTitularyFeature
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df84b108190b4407a72a3500af9 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.