Triple
T29969913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Liang |
E761287
|
entity |
| Predicate | preliminaryCompiler |
P67004
|
FINISHED |
| Object | Yao Cha |
—
|
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: Yao Cha | Statement: [Book of Liang, preliminaryCompiler, Yao Cha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preliminaryCompiler Context triple: [Book of Liang, preliminaryCompiler, Yao Cha]
-
A.
formerCompiler
Indicates that an entity previously served as a compiler (e.g., of texts, code, or documents) for another entity but no longer holds that role.
-
B.
textCompiler
chosen
Indicates that one entity functions as a compiler that processes, transforms, or translates text associated with another entity.
-
C.
compiler
Indicates that one entity serves as a compiler of another, typically transforming source material (such as code or documents) into a compiled or aggregated form.
-
D.
compilation
Indicates the process or result of collecting and assembling various items, works, or elements into a single organized whole.
-
E.
predecessorCompiledBy
Indicates that one entity was compiled by the same agent or process before another entity was compiled.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786d6e108190b7f631c222899519 |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:31 p.m.