Triple
T5624918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard Business School campus core |
E147693
|
entity |
| Predicate | campusFunction |
P33110
|
FINISHED |
| Object | MBA program instruction |
—
|
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: MBA program instruction | Statement: [Harvard Business School campus core, campusFunction, MBA program instruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusFunction Context triple: [Harvard Business School campus core, campusFunction, MBA program instruction]
-
A.
campusFacility
Indicates that one entity is a facility that is located on or belongs to a particular campus.
-
B.
campusUse
chosen
Indicates that something is intended for, associated with, or occurring in the use or activities of a campus or campus community.
-
C.
cityCampusServes
Indicates that a city campus provides services, resources, or support to a particular population, area, or institution.
-
D.
campusArea
Indicates that one entity is the physical area or spatial extent of a campus associated with another entity.
-
E.
campus
Indicates that an entity is located on, associated with, or taking place within a particular 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022165d8c8190b2a14f1cd0a45ecc |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.