Triple
T17207437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2012 Pekan Olahraga Nasional |
E417636
|
entity |
| Predicate | hasEventFormat |
P46686
|
FINISHED |
| Object | multi-discipline tournament |
—
|
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: multi-discipline tournament | Statement: [2012 Pekan Olahraga Nasional, hasEventFormat, multi-discipline tournament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventFormat Context triple: [2012 Pekan Olahraga Nasional, hasEventFormat, multi-discipline tournament]
-
A.
hasFormatElement
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
B.
hasFormatSpecification
Indicates that something is associated with a particular format definition or specification that describes how it should be structured or represented.
-
C.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
-
D.
hasMatchFormat
chosen
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
-
E.
hasTicketFormat
Indicates that an entity’s ticket is expressed or structured in a particular format.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc283648190b2c1f957940024aa |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.