Triple
T29202648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fancheng |
E740320
|
entity |
| Predicate | heldByAfterBattle |
P109227
|
FINISHED |
| Object | Mongol Empire |
—
|
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: Mongol Empire | Statement: [Battle of Fancheng, heldByAfterBattle, Mongol Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByAfterBattle Context triple: [Battle of Fancheng, heldByAfterBattle, Mongol Empire]
-
A.
heldAfter
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
-
B.
ownedByDuringBattle
Indicates that one entity possessed or controlled another entity specifically during the time span of a particular battle.
-
C.
statusAfterBattle
chosen
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
D.
heldByEnd
Indicates that an object or item is being held or supported specifically at one of its ends by an agent or another object.
-
E.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c6905c81908c183f248bd3a7aa |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:07 p.m.