Triple
T8080153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNTV |
E188592
|
entity |
| Predicate | hasCommunityOutreach |
P67233
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [UNTV, hasCommunityOutreach, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityOutreach Context triple: [UNTV, hasCommunityOutreach, yes]
-
A.
hasOutreachComponent
chosen
Indicates that something includes or is associated with an outreach-related element, activity, or component.
-
B.
hasCommunityService
Indicates that an entity is associated with, participates in, or is subject to community service activities or obligations.
-
C.
hasCommunityEfforts
Indicates that an entity engages in or is associated with organized activities or initiatives intended to benefit a community.
-
D.
hasCommunityInstitutions
Indicates that an entity possesses, hosts, or is associated with organized community-serving institutions (such as local organizations, centers, or facilities) within its scope.
-
E.
hasCommunityServed
Indicates that an entity provides services or benefits to, or is intended to support, a particular community or group of people.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a504d48190ace96e814d99b182 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.