Triple
T8350493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinhala Only policy |
E196144
|
entity |
| Predicate | promptedDemandFor |
P82228
|
FINISHED |
| Object | federalism in Sri Lanka |
—
|
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: federalism in Sri Lanka | Statement: [Sinhala Only policy, promptedDemandFor, federalism in Sri Lanka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promptedDemandFor Context triple: [Sinhala Only policy, promptedDemandFor, federalism in Sri Lanka]
-
A.
demanded
Indicates that one entity forcefully or insistently requested something from another entity.
-
B.
demands
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
C.
releasedOnDemandOf
Indicates that one entity is released or set free as a direct result of another entity’s request, order, or demand.
-
D.
demand
Indicates that one entity requests or insists that another entity provide something or perform an action, often with an expectation of compliance.
-
E.
needBased
Indicates that something is determined, allocated, or provided according to the level of need rather than uniform or fixed criteria.
- F. None of above. chosen
Provenance (4 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80181ca48190bbf2e6a6aae80d69 |
completed | March 31, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:59 p.m.