Triple
T36404636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadium Merdeka |
E896717
|
entity |
| Predicate | significantEventCountry |
P153335
|
FINISHED |
| Object | Federation of Malaya |
—
|
NE NERFINISHED |
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: Federation of Malaya | Statement: [Stadium Merdeka, significantEventCountry, Federation of Malaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantEventCountry Context triple: [Stadium Merdeka, significantEventCountry, Federation of Malaya]
-
A.
majorEventCountry
chosen
Indicates that a major event took place in, or is primarily associated with, a particular country.
-
B.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
C.
significantEventPlace
Indicates the place where a significant event occurred or is associated with an entity.
-
D.
notableInternationalEvents
Indicates that the subject is associated with significant events that have international relevance or impact.
-
E.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:10 p.m.