Triple
T5650760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trevelyan College |
E124501
|
entity |
| Predicate | residentialStatus |
P25942
|
FINISHED |
| Object | residential college |
—
|
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: residential college | Statement: [Trevelyan College, residentialStatus, residential college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residentialStatus Context triple: [Trevelyan College, residentialStatus, residential college]
-
A.
isResidential
chosen
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
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.
residenceUsedFor
Indicates that a particular residence is used for a specific purpose, function, or activity.
-
E.
propertyStatus
Indicates the current condition, state, or classification assigned to a property within a given context (e.g., availability, legal standing, or operational state).
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d4ca788190b20168b20cb1d030 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.