Triple
T6061143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul Olympic Stadium |
E135033
|
entity |
| Predicate | partOfEventInfrastructure |
P19374
|
FINISHED |
| Object | 1988 Summer Olympics venues |
—
|
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: 1988 Summer Olympics venues | Statement: [Seoul Olympic Stadium, partOfEventInfrastructure, 1988 Summer Olympics venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfEventInfrastructure Context triple: [Seoul Olympic Stadium, partOfEventInfrastructure, 1988 Summer Olympics venues]
-
A.
partOfEvent
Indicates that one entity is a component, segment, or sub-activity that belongs to or occurs within a larger event.
-
B.
isPartOfInfrastructure
chosen
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
-
C.
partOfFacility
Indicates that one entity is a component, section, or sub-unit belonging to a larger facility.
-
D.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
E.
sportsFacility
Indicates that one entity is a sports facility where sports or physical activities can take place for the other 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0571fcecc8190a68e0d0668bbbfa7 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.