Triple
T22915147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean Tour |
E568715
|
entity |
| Predicate | primaryParticipantsNationality |
P99870
|
FINISHED |
| Object | South Korean |
—
|
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: South Korean | Statement: [Korean Tour, primaryParticipantsNationality, South Korean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryParticipantsNationality Context triple: [Korean Tour, primaryParticipantsNationality, South Korean]
-
A.
hasParticipantNationality
chosen
Indicates that a participant in an event, activity, or relation has a specific nationality.
-
B.
targetNationality
Indicates that one entity has the specified nationality as its intended or designated target.
-
C.
primaryNationality
Indicates the main national affiliation or citizenship that most strongly characterizes an entity among possibly multiple nationalities.
-
D.
parentsNationality
Indicates that it specifies the country or nationality associated with a person's parent or parents.
-
E.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18078077881908b8124cc22110c6e |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.