Triple
T28076060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chu Shi Biao |
E709544
|
entity |
| Predicate | valueIn |
P49807
|
FINISHED |
| Object | Confucian political thought |
—
|
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: Confucian political thought | Statement: [Chu Shi Biao, valueIn, Confucian political thought]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueIn Context triple: [Chu Shi Biao, valueIn, Confucian political thought]
-
A.
valuesIn
Indicates that one entity specifies or constrains the set of permissible values for another entity.
-
B.
value
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
-
C.
valueDefinedBy
Indicates that the value of one entity is determined, specified, or constrained by another entity.
-
D.
valueExpressed
chosen
Indicates that a particular value, opinion, or quantitative measure is articulated, represented, or made explicit by an entity or expression.
-
E.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 8:49 p.m.