Triple
T38395960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kapalong |
E900761
|
entity |
| Predicate | hasRegionalSubdivisionName |
P87501
|
FINISHED |
| Object | Davao Region |
E47878
|
NE 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: Davao Region | Statement: [Kapalong, hasRegionalSubdivisionName, Davao Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalSubdivisionName Context triple: [Kapalong, hasRegionalSubdivisionName, Davao Region]
-
A.
hasRegionalName
Indicates that an entity is known by a specific name or designation within a particular region or locality.
-
B.
hasSubdivisionName3
chosen
Indicates that an entity has a third-level subdivision whose name is given by the associated value.
-
C.
hasStateSubdivisionName
Indicates that an entity has a specific name for one of its internal state-level subdivisions.
-
D.
isRegionalSubdivisionOf
Indicates that one region functions as an administrative or geographic subdivision within a larger region.
-
E.
hasSubdivisionLabel
Indicates that an entity assigns a specific label or name to one of its subdivisions or component parts.
- F. None of above.
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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41e015139c8190983b97753e3045f1 |
completed | June 29, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.