Triple
T33842574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gapuwiyak |
E867393
|
entity |
| Predicate | isHomelandHub |
P177780
|
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: [Gapuwiyak, isHomelandHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHomelandHub Context triple: [Gapuwiyak, isHomelandHub, true]
-
A.
hasHomeland
Indicates that an entity considers or recognizes a particular place or region as its homeland or place of origin.
-
B.
wasHomelandIn
Indicates that a location historically served as the homeland or place of origin for a specified group or entity.
-
C.
isResidentialHubIn
Indicates that a location functions primarily as a residential center or hub within a specified larger area or region.
-
D.
isCommunityHub
Indicates that a place or entity functions as a central gathering point or focal location for community activities, services, and interactions.
-
E.
isMajorHubInCountry
Indicates that a location functions as a primary or central hub within a specified country, typically in terms of transport, commerce, or connectivity.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:47 a.m.