Triple
T28652898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament Complex, Sri Jayawardenepura Kotte |
E725248
|
entity |
| Predicate | openedForUseByParliament |
P44506
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Parliament Complex, Sri Jayawardenepura Kotte, openedForUseByParliament, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForUseByParliament Context triple: [Parliament Complex, Sri Jayawardenepura Kotte, openedForUseByParliament, 1982]
-
A.
usedInParliament
Indicates that something (such as a procedure, term, rule, or item) is employed or applied within the context of a parliamentary body or its activities.
-
B.
openedForUseBy
chosen
Indicates that something has been made available or activated so that a particular entity can use it.
-
C.
reopenedAsParliament
Indicates that an institution or building was reopened with the status or function of a parliament.
-
D.
usesParliament
Indicates that one entity conducts its legislative or decision‑making processes through a parliamentary body or system.
-
E.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 4:53 a.m.