Triple
T33918601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kappa Alpha Psi |
E869537
|
entity |
| Predicate | historicallyServes |
P19592
|
FINISHED |
| Object | African American students |
—
|
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: African American students | Statement: [Kappa Alpha Psi, historicallyServes, African American students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyServes Context triple: [Kappa Alpha Psi, historicallyServes, African American students]
-
A.
historicallyServedBy
chosen
Indicates that an entity was provided with services or support by another entity during a past period of time.
-
B.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
-
C.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
D.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
E.
servesHistoricTown
Indicates that a service, route, or facility provides access or support to a town recognized for its historical significance.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
Created at: May 1, 2026, 1:49 a.m.