Triple
T6311713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyeongchang Olympic Stadium |
E141518
|
entity |
| Predicate | permanentOrTemporary |
P50685
|
FINISHED |
| Object | temporary |
—
|
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: temporary | Statement: [Pyeongchang Olympic Stadium, permanentOrTemporary, temporary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentOrTemporary Context triple: [Pyeongchang Olympic Stadium, permanentOrTemporary, temporary]
-
A.
isTemporary
chosen
Indicates that the relationship, state, or condition holds only for a limited or non-permanent duration.
-
B.
isPermanentForMembers
Indicates that a condition, status, or setting is unchangeable and remains in effect indefinitely for the members it applies to.
-
C.
isPermanentOffice
Indicates that an office or position is established on a lasting, ongoing basis rather than being temporary or time-limited.
-
D.
permanence
Indicates that a state, condition, or relationship continues to hold over time without significant change or interruption.
-
E.
isPermanentBody
Indicates that an entity functions as an enduring, officially established body or organization that is not temporary or ad hoc.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0649d1e048190a3fc7fbce9d2ee57 |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.