Triple
T24935300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Busan (1592) |
E623295
|
entity |
| Predicate | outcomeForDefender |
P6933
|
FINISHED |
| Object | destruction of Busan garrison |
—
|
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: destruction of Busan garrison | Statement: [Siege of Busan (1592), outcomeForDefender, destruction of Busan garrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForDefender Context triple: [Siege of Busan (1592), outcomeForDefender, destruction of Busan garrison]
-
A.
defenseResult
chosen
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
B.
awardedToDefenders
Indicates that something (such as a title, honor, or recognition) is granted specifically to entities serving in a defensive role.
-
C.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
D.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
E.
tacticalOutcome
Indicates the specific result or consequence produced by a particular tactic or tactical action in a given situation.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:30 a.m.