Triple
T30590721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changli Xiansheng |
E778645
|
entity |
| Predicate | eraOfBearer |
P175270
|
FINISHED |
| Object | Mid-Tang period |
—
|
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: Mid-Tang period | Statement: [Changli Xiansheng, eraOfBearer, Mid-Tang period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfBearer Context triple: [Changli Xiansheng, eraOfBearer, Mid-Tang period]
-
A.
bearerType
Indicates the type or category of entity that serves as the bearer or holder in a given relationship or context.
-
B.
bearerAnglicizedNameOf
Indicates that one entity is the anglicized (English-adapted) version of the name borne by another entity.
-
C.
bearerInstanceOf
Indicates that a bearer (such as an agent, object, or entity) is an instance or specific realization of a more general class, type, or role.
-
D.
bearerFounded
Indicates that the bearer (such as a person or organization) is the one who established or created the associated entity (such as a company, institution, or project).
-
E.
bearerByname
Indicates that an entity is known or referred to by a particular byname or secondary name.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 29, 2026, 8:24 p.m.