Triple
T19059990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertford College Hall |
E466502
|
entity |
| Predicate | gatheringPlaceFor |
P16368
|
FINISHED |
| Object | Hertford College community |
—
|
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: Hertford College community | Statement: [Hertford College Hall, gatheringPlaceFor, Hertford College community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gatheringPlaceFor Context triple: [Hertford College Hall, gatheringPlaceFor, Hertford College community]
-
A.
gatheringPlace
chosen
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
B.
traditionalMeetingPlace
Indicates that a location is customarily used as a gathering spot for meetings or social interactions according to established tradition.
-
C.
meetingPlaceOf
Indicates the location where a particular meeting or gathering takes place or is held for the referenced entities.
-
D.
targetedPlace
Indicates that an entity intentionally directed an action, operation, or influence toward a specific place or location.
-
E.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc0910088190b042095937b202a8 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.