Triple
T3159111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Media |
E66061
|
entity |
| Predicate | conferredAfterEvent |
P18219
|
FINISHED |
| Object | conquest of the Median Empire |
—
|
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: conquest of the Median Empire | Statement: [King of Media, conferredAfterEvent, conquest of the Median Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferredAfterEvent Context triple: [King of Media, conferredAfterEvent, conquest of the Median Empire]
-
A.
conferredOn
chosen
Indicates that something (such as an honor, title, degree, or benefit) has been formally granted or bestowed upon a particular entity.
-
B.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
-
C.
conferredIn
Indicates that something (such as a degree, title, or honor) was formally granted or awarded within a particular context, event, or institution.
-
D.
concludedAtEvent
Indicates that an entity’s participation, state, or validity ended as a result of a specific event.
-
E.
heldAfter
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5ed82a08190a1bdcf18ee593c79 |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.