Triple
T1326108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlanta University Center |
E28329
|
entity |
| Predicate | collaborationArea |
P26572
|
FINISHED |
| Object | academic programs |
—
|
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: academic programs | Statement: [Atlanta University Center, collaborationArea, academic programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationArea Context triple: [Atlanta University Center, collaborationArea, academic programs]
-
A.
platformCollaboration
Indicates a collaborative relationship where multiple entities work together or integrate their efforts on or through a shared platform.
-
B.
collaborationModel
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
C.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
D.
engagementArea
Indicates the spatial region or scope within which an entity’s actions, influence, or interactions are intended to occur.
-
E.
areaComponent
Indicates that one area is a constituent or sub-area that forms part of a larger area.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19fd2648190932a85eacb3e7ec4 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf8158ac8190b8360ecccc2980bc |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:55 p.m.