Triple
T29996015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry A. Gampel |
E762024
|
entity |
| Predicate | hasNamesakeBuildingAt |
P49744
|
FINISHED |
| Object | University of Connecticut |
—
|
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: University of Connecticut | Statement: [Harry A. Gampel, hasNamesakeBuildingAt, University of Connecticut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeBuildingAt Context triple: [Harry A. Gampel, hasNamesakeBuildingAt, University of Connecticut]
-
A.
hasBuildingNamedAfterHim
chosen
Indicates that a person has a building that is named in their honor.
-
B.
notableBuildingAssociated
Indicates a relationship where a notable or significant building is associated with, connected to, or relevant to a given entity.
-
C.
emblematicBuildingLocation
Indicates that a building serves as a symbolic or representative landmark for a particular location or area.
-
D.
hasFamousStructure
Indicates that an entity possesses or is associated with a well-known or widely recognized structure.
-
E.
foundingBuilding
Indicates that a particular building is the original or primary structure where an organization, institution, or entity was founded.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 29, 2026, 6:40 p.m.