Triple
T30791169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provincial Councils of Sri Lanka |
E784097
|
entity |
| Predicate | hasListOfSubjects |
P106967
|
FINISHED |
| Object | Provincial Council List (List I) |
—
|
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: Provincial Council List (List I) | Statement: [Provincial Councils of Sri Lanka, hasListOfSubjects, Provincial Council List (List I)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListOfSubjects Context triple: [Provincial Councils of Sri Lanka, hasListOfSubjects, Provincial Council List (List I)]
-
A.
hasHumanSubject
Indicates that an entity serves as the human participant or subject involved in an action, event, or relation.
-
B.
hasCollectionSubject
chosen
Indicates that a collection is about or thematically centered on a particular subject.
-
C.
hasSubjectCount
Indicates that an entity is associated with a specific number of subjects.
-
D.
hasPrimarySubject
Indicates that an entity is the main or principal subject associated with another entity or resource.
-
E.
hasSubjectTypes
Indicates that an entity is associated with one or more specific subject categories or types.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 29, 2026, 8:42 p.m.