Triple
T25823790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampden Sydney, Virginia |
E650469
|
entity |
| Predicate | hasCampusDominatingCommunity |
P171738
|
FINISHED |
| Object | Hampden–Sydney College |
—
|
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: Hampden–Sydney College | Statement: [Hampden Sydney, Virginia, hasCampusDominatingCommunity, Hampden–Sydney College]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampusDominatingCommunity Context triple: [Hampden Sydney, Virginia, hasCampusDominatingCommunity, Hampden–Sydney College]
-
A.
hasCampusCommunity
Indicates that an institution or location possesses an associated campus-based community or group of people connected to it.
-
B.
hasCampusOn
Indicates that an institution or organization maintains a campus located on a specified geographic area or site.
-
C.
hasMajorCommunity
Indicates that an entity possesses a primary or significantly large community associated with it.
-
D.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
E.
hasCampusCity
Indicates that an educational institution or campus is located in a particular city.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 22, 2026, 7:31 a.m.