Triple
T27929987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gadeokdo New Airport |
E707952
|
entity |
| Predicate | intendedOpeningRole |
P21890
|
FINISHED |
| Object | new main airport for Busan region |
—
|
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: new main airport for Busan region | Statement: [Gadeokdo New Airport, intendedOpeningRole, new main airport for Busan region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedOpeningRole Context triple: [Gadeokdo New Airport, intendedOpeningRole, new main airport for Busan region]
-
A.
openingRole
Indicates the functional role or position an entity holds at the initial or starting phase of an event, process, or sequence.
-
B.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
C.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
D.
plannedRole
chosen
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
E.
engagementRole
Indicates the specific function, capacity, or responsibility an entity assumes within a particular engagement or interaction.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 7:02 p.m.