Triple
T28374337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lü |
E718715
|
entity |
| Predicate | sourceTraditions |
P167912
|
FINISHED |
| Object | Chinese historiography |
—
|
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: Chinese historiography | Statement: [Lü, sourceTraditions, Chinese historiography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceTraditions Context triple: [Lü, sourceTraditions, Chinese historiography]
-
A.
religiousTextTradition
Indicates that a religious text is associated with, originates from, or is authoritative within a particular religious tradition or denomination.
-
B.
spiritualityType
Indicates the specific kind or category of spirituality associated with an entity.
-
C.
spiritualityInfluencedBy
Indicates that one entity’s spirituality, spiritual beliefs, or practices are shaped, guided, or affected by another entity.
-
D.
BuddhistTradition
Indicates that an entity follows, embodies, or is associated with Buddhist religious, philosophical, or cultural traditions.
-
E.
religiousTraditions
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 1:02 a.m.