Triple
T23814195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mambajao |
E589045
|
entity |
| Predicate | primaryAdministrativeRole |
P153647
|
FINISHED |
| Object | administrative center of Camiguin Island |
—
|
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: administrative center of Camiguin Island | Statement: [Mambajao, primaryAdministrativeRole, administrative center of Camiguin Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAdministrativeRole Context triple: [Mambajao, primaryAdministrativeRole, administrative center of Camiguin Island]
-
A.
principalRoleIn
Indicates that an entity holds the primary or leading role in a particular context, activity, or relationship.
-
B.
primaryRoleInHierarchy
Indicates that one entity holds the main or most important role or position within a defined hierarchy relative to another entity.
-
C.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
D.
primaryServiceRole
Indicates the main or most important functional role that a service performs in relation to other entities or processes.
-
E.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7a9ce708190a27195d58589d757 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:57 p.m.