Triple
T32801224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bintulu campus |
E838899
|
entity |
| Predicate | hasTertiaryRole |
P6239
|
FINISHED |
| Object | community engagement |
—
|
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: community engagement | Statement: [Bintulu campus, hasTertiaryRole, community engagement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTertiaryRole Context triple: [Bintulu campus, hasTertiaryRole, community engagement]
-
A.
hasAuxiliaryRole
chosen
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
B.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
C.
laterPrimaryRole
Indicates that an entity assumes a specified primary role at a later time than another role or state in a sequence.
-
D.
hasStructureRole
Indicates that an entity serves a specific functional or positional role within a larger structure or organizational arrangement.
-
E.
hasTerminusRole
Indicates that an entity participates in something specifically in the capacity of a terminus or endpoint role.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:14 a.m.