Triple
T29202647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fancheng |
E740320
|
entity |
| Predicate | heldByBeforeBattle |
P24450
|
FINISHED |
| Object | Southern Song dynasty |
—
|
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: Southern Song dynasty | Statement: [Battle of Fancheng, heldByBeforeBattle, Southern Song dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByBeforeBattle Context triple: [Battle of Fancheng, heldByBeforeBattle, Southern Song dynasty]
-
A.
ownedByDuringBattle
Indicates that one entity possessed or controlled another entity specifically during the time span of a particular battle.
-
B.
heldBefore
chosen
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
C.
allyInBattle
Indicates that two or more entities cooperate on the same side as partners during a specific battle or combat situation.
-
D.
heldOf
Indicates that something is possessed, controlled, or kept by a particular entity.
-
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_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:07 p.m.