Triple
T33526114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 周公 |
E858643
|
entity |
| Predicate | 相关典籍 |
P177068
|
FINISHED |
| Object | 尚书 |
—
|
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: 尚书 | Statement: [周公, 相关典籍, 尚书]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 相关典籍 Context triple: [周公, 相关典籍, 尚书]
-
A.
relatedLibrary
Indicates that one library has a meaningful connection or association with another library, such as dependency, compatibility, or functional similarity.
-
B.
isAssociatedWithReligiousText
Indicates a relationship where an entity is connected or linked in some way to a religious text, such as being based on, derived from, or directly related to it.
-
C.
knowledgeSourceInCanon
Indicates that the specified source of information is part of the officially recognized canon within a given universe or body of work.
-
D.
associatedBiblicalBook
Indicates that one entity is linked or connected to a specific book of the Bible as its relevant or referenced scriptural source.
-
E.
religiousTextAttestedIn
Indicates that the existence or content of a religious text is supported, recorded, or evidenced in a particular source, context, or medium.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85ca7c0819098069384b0d1ca6a |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:39 a.m.