Triple
T17801163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barangay Kapasigan |
E444428
|
entity |
| Predicate | isLocalCommunity |
P81476
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Barangay Kapasigan, isLocalCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalCommunity Context triple: [Barangay Kapasigan, isLocalCommunity, true]
-
A.
isLocalAdministrativeCommunity
chosen
Indicates that one entity functions as a local administrative community with respect to another entity, typically providing local governance or administrative coordination.
-
B.
hasLocalCommunities
Indicates that an entity is associated with or contains smaller, localized community groups within a specific area or region.
-
C.
isCommunityOf
Indicates that one entity functions as a community composed of, or defined by, the members or elements represented by the other entity.
-
D.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
E.
isRemoteCommunity
Indicates that a community is geographically isolated or distant from urban centers and services.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487ff42108190b82ceb4466aa2dff |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.