Triple
T34540311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pungdo Island |
E886787
|
entity |
| Predicate | hasNearbySeaBattle |
P117087
|
FINISHED |
| Object | Battle of Pungdo |
—
|
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: Battle of Pungdo | Statement: [Pungdo Island, hasNearbySeaBattle, Battle of Pungdo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbySeaBattle Context triple: [Pungdo Island, hasNearbySeaBattle, Battle of Pungdo]
-
A.
hasIslandNearby
Indicates that one location is situated close to an island in geographic space.
-
B.
hasNearbyMarineFeature
chosen
Indicates that one entity is located close to a marine geographic feature associated with the other entity.
-
C.
hasNavalPresenceIn
Indicates that an entity maintains or deploys naval forces or maritime assets within a specified geographic area or location.
-
D.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
E.
hasNearbyCoastalSettlement
Indicates that one entity has a coastal settlement located in close geographic proximity to it.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: May 1, 2026, 2:02 a.m.