Triple
T16579265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bato the Daesitiate |
E402795
|
entity |
| Predicate | surrenderTime |
P41942
|
FINISHED |
| Object | AD 9 |
—
|
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: AD 9 | Statement: [Bato the Daesitiate, surrenderTime, AD 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surrenderTime Context triple: [Bato the Daesitiate, surrenderTime, AD 9]
-
A.
surrenderedAfter
Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
-
B.
surrenderEffectiveTime
chosen
Indicates the point in time at which a surrender (e.g., of rights, ownership, or an agreement) becomes legally or practically effective.
-
C.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
D.
surrenderEvent
Indicates an event in which one party yields or gives up control, rights, or resistance to another party.
-
E.
surrenderAcceptedBy
Indicates that one party’s act of surrender is formally received and agreed to by another party.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3595f9be88190b01ba628ecf1103d |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.