Triple
T19191780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangsamoro Liberation Organization |
E469855
|
entity |
| Predicate | populationTarget |
P17586
|
FINISHED |
| Object | Bangsamoro population |
—
|
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: Bangsamoro population | Statement: [Bangsamoro Liberation Organization, populationTarget, Bangsamoro population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationTarget Context triple: [Bangsamoro Liberation Organization, populationTarget, Bangsamoro population]
-
A.
population
Indicates the total number of individuals living in or present within a specified area or group.
-
B.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
C.
populationFocus
Indicates that something is primarily directed toward, concerned with, or designed for a particular population or demographic group.
-
D.
populationClass
Indicates a categorical classification of a population based on shared characteristics, status, or demographic criteria.
-
E.
targetedPopulation
chosen
Indicates the group of individuals or entities that an action, intervention, or effect is specifically directed toward.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a226dc8190a8a96960a4180298 |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.