Triple
T15697304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biomedical Engineering Building |
E380496
|
entity |
| Predicate | usedByDepartment |
P120343
|
FINISHED |
| Object | biomedical engineering department |
—
|
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: biomedical engineering department | Statement: [Biomedical Engineering Building, usedByDepartment, biomedical engineering department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByDepartment Context triple: [Biomedical Engineering Building, usedByDepartment, biomedical engineering department]
-
A.
basedInDepartment
Indicates that an entity operates or has its primary affiliation within a specific department.
-
B.
usedByDivision
Indicates that something (such as a resource, tool, or asset) is utilized or employed by a particular division within an organization.
-
C.
offeredByDepartment
Indicates that something, such as a course or program, is provided or made available by a specific department.
-
D.
worksInDepartment
Indicates that an entity is employed in and performs their job duties within a particular department.
-
E.
supportsDepartment
Indicates that one entity provides assistance, resources, or backing to a specific department.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0b4d01c9c81909f6b611e8144c838 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 10, 2026, 4:44 a.m.