Triple
T28244124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chen Shou |
E712112
|
entity |
| Predicate | usedSourcesFrom |
P39729
|
FINISHED |
| Object | state archives of Shu Han |
—
|
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: state archives of Shu Han | Statement: [Chen Shou, usedSourcesFrom, state archives of Shu Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSourcesFrom Context triple: [Chen Shou, usedSourcesFrom, state archives of Shu Han]
-
A.
usedAsSourceIn
chosen
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
-
B.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
C.
usedAsNameSourceFor
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
-
D.
laterSources
Indicates that the information, claim, or reference is derived from sources that were created or recorded at a later time than the event or material being discussed.
-
E.
requiresSources
Indicates that something must be supported, justified, or validated by one or more external sources.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c77edc8190bb23727297adb769 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 11 p.m.