Triple
T28766012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sarhu |
E726269
|
entity |
| Predicate | tacticUsedByLaterJin |
P100860
|
FINISHED |
| Object | ambush |
—
|
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: ambush | Statement: [Battle of Sarhu, tacticUsedByLaterJin, ambush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticUsedByLaterJin Context triple: [Battle of Sarhu, tacticUsedByLaterJin, ambush]
-
A.
tacticInspiredBy
Indicates that a tactic is derived from, influenced by, or modeled after another tactic or source.
-
B.
tacticalFeatureUsed
chosen
Indicates that a specific tactical feature, maneuver, or capability is employed or brought into play within a tactical situation or operation.
-
C.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
D.
tacticsManualUsedBy
Indicates that a tactics manual is utilized or applied by a particular agent or entity.
-
E.
BaekjeStrategy
Indicates a strategic relationship in which actions, plans, or policies are aligned with or derived from the military, political, or diplomatic strategies historically associated with Baekje.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:13 a.m.