Triple
T20257953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hwangsanbeol |
E498752
|
entity |
| Predicate | SillaOutcome |
P59870
|
FINISHED |
| Object | strategic advantage over Baekje |
—
|
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: strategic advantage over Baekje | Statement: [Battle of Hwangsanbeol, SillaOutcome, strategic advantage over Baekje]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SillaOutcome Context triple: [Battle of Hwangsanbeol, SillaOutcome, strategic advantage over Baekje]
-
A.
chairIn
Indicates that one entity is a chair located within the spatial bounds or interior of another entity.
-
B.
canChair
Indicates that an entity has the authority or capability to preside over, lead, or chair a meeting, committee, or similar group.
-
C.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
seatIs
Indicates that one entity functions as the seat or seating position of another entity.
-
E.
seatOn
Indicates that one entity is positioned or placed on a seat or seating surface associated with another entity.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674c7296c819092860942de8f28d5 |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.