Triple
T24704171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jangsaengpo Port |
E611840
|
entity |
| Predicate | hasNearbyFestival |
P45864
|
FINISHED |
| Object | Ulsan Whale Festival |
—
|
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: Ulsan Whale Festival | Statement: [Jangsaengpo Port, hasNearbyFestival, Ulsan Whale Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyFestival Context triple: [Jangsaengpo Port, hasNearbyFestival, Ulsan Whale Festival]
-
A.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
B.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
C.
hasNearbyEvent
chosen
Indicates that an event occurs close in space or time to the referenced entity.
-
D.
hostedEventsNearby
Indicates that an entity has organized or is responsible for events occurring within a nearby geographic area relative to another reference point.
-
E.
hasFestivalContext
Indicates that something is related to, occurs within, or is characterized by the setting, activities, or circumstances of a festival.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 3:23 a.m.