Triple
T20567066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wen Gong |
E504991
|
entity |
| Predicate | honorsReputation |
P2354
|
FINISHED |
| Object | Zhu Xi’s scholarly prestige |
—
|
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: Zhu Xi’s scholarly prestige | Statement: [Wen Gong, honorsReputation, Zhu Xi’s scholarly prestige]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsReputation Context triple: [Wen Gong, honorsReputation, Zhu Xi’s scholarly prestige]
-
A.
placeInReputation
Indicates that an entity holds a particular standing, status, or level within a reputation or ranking system.
-
B.
honors
chosen
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
C.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
D.
isHonor
Indicates that one entity is regarded as an honor, distinction, or source of prestige for another entity.
-
E.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a33f7c8190966da03528dfe8aa |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.