Triple
T10496054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havemeyer Hall |
E247538
|
entity |
| Predicate | campusBuildingNumber |
P75186
|
FINISHED |
| Object | 300-level series |
—
|
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: 300-level series | Statement: [Havemeyer Hall, campusBuildingNumber, 300-level series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusBuildingNumber Context triple: [Havemeyer Hall, campusBuildingNumber, 300-level series]
-
A.
buildingNumber
chosen
Indicates the specific numeric identifier assigned to a building within an address or location.
-
B.
campusStructure
Indicates a structural or organizational relationship between parts of a campus and the campus as a whole (e.g., buildings, facilities, or areas belonging to or forming the campus).
-
C.
campusFacility
Indicates that one entity is a facility that is located on or belongs to a particular campus.
-
D.
campus1
Indicates a relationship where an entity is identified as a campus or is located on/associated with a particular campus.
-
E.
campusLandmark
Indicates that something serves as a notable or recognizable landmark located on or associated with a 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098cd82c8190b44127a66c9c75ae |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:24 p.m.