Triple
T27955958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ma Chao |
E703548
|
entity |
| Predicate | roleInShu |
P194847
|
FINISHED |
| Object | senior general under Liu Bei |
—
|
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: senior general under Liu Bei | Statement: [Ma Chao, roleInShu, senior general under Liu Bei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInShu Context triple: [Ma Chao, roleInShu, senior general under Liu Bei]
-
A.
roleInShinKokinWakashu
Indicates the specific role or involvement an entity has in relation to the Shin Kokin Wakashū (e.g., as compiler, editor, or contributor).
-
B.
shiteRole
Indicates that one entity serves in a particular role, function, or capacity in relation to another entity.
-
C.
roleInAnime
Indicates that an entity holds a specific character role or participation in a particular anime work.
-
D.
roleInKonkokyo
Indicates the specific position, office, or function an entity holds within the Konkokyo religious organization.
-
E.
roleInShinto
Indicates that an entity holds a particular function, status, or significance within the context of Shinto beliefs, practices, or institutions.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_69fd8ccaee848190acd59d7d643ad062 |
completed | May 8, 2026, 7:12 a.m. |
Created at: April 27, 2026, 7:28 p.m.