Triple
T23525127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yi I |
E574610
|
entity |
| Predicate | passedCivilServiceExam |
P19062
|
FINISHED |
| Object | at age 13 |
—
|
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: at age 13 | Statement: [Yi I, passedCivilServiceExam, at age 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passedCivilServiceExam Context triple: [Yi I, passedCivilServiceExam, at age 13]
-
A.
passedExam
chosen
Indicates that an entity has successfully met the required criteria to pass a particular exam.
-
B.
passed
Indicates that one entity successfully transferred control, responsibility, or an item (such as an object, message, or test) to another entity or through a specified stage or condition.
-
C.
passes
Indicates that one entity successfully transfers, hands over, or moves something (such as an object, message, or responsibility) to another entity.
-
D.
allegedToHavePassed
Indicates that one entity is claimed or accused, without confirmed proof, to have transferred or enacted something (such as a law, document, or item) to another.
-
E.
pass
Indicates that one entity successfully transfers or moves something (such as an object, information, or a turn) 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1ac72bfb88190b7da3837e66e851c |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.