Triple
T11717064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goddard College |
E278525
|
entity |
| Predicate | residencyStructure |
P6740
|
FINISHED |
| Object | periodic on-campus residencies |
—
|
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: periodic on-campus residencies | Statement: [Goddard College, residencyStructure, periodic on-campus residencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residencyStructure Context triple: [Goddard College, residencyStructure, periodic on-campus residencies]
-
A.
residencyPattern
chosen
Indicates the typical way an entity resides or occupies a place over time, such as its usual location, duration, or frequency of stay.
-
B.
residencyStatus
Indicates the legal or official residential classification of an entity within a particular jurisdiction or context.
-
C.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
D.
residencyLocation
Indicates the place where an entity lives or maintains its primary residence.
-
E.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c10d988190842acd824135cf15 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.