Triple
T30109828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgan State University |
E765233
|
entity |
| Predicate | hasExtensionCampus |
P116
|
FINISHED |
| Object | Harbor East campus |
—
|
NE NERFINISHED |
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: Harbor East campus | Statement: [Morgan State University, hasExtensionCampus, Harbor East campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExtensionCampus Context triple: [Morgan State University, hasExtensionCampus, Harbor East campus]
-
A.
hasSurfaceCampus
Indicates that one entity (typically an institution) maintains a physical campus or site located on the surface of another entity (such as a planet or celestial body).
-
B.
hasCampusOn
Indicates that an institution or organization maintains a campus located on a specified geographic area or site.
-
C.
hasCampusFeature
Indicates that a campus possesses or includes a specific physical or functional feature.
-
D.
isCampusFor
Indicates that a location serves as the campus associated with a particular institution or organization.
-
E.
hasAdditionalCampus
chosen
Indicates that an educational institution maintains one or more campuses in addition to its primary or main campus.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 7:10 p.m.