Triple
T2719364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RISD Residence Halls |
E60044
|
entity |
| Predicate | hasSupportService |
P41839
|
FINISHED |
| Object | resident assistants |
—
|
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: resident assistants | Statement: [RISD Residence Halls, hasSupportService, resident assistants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupportService Context triple: [RISD Residence Halls, hasSupportService, resident assistants]
-
A.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
B.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
C.
hasServiceCenter
Indicates that an entity maintains or is associated with a service center that provides support, repair, or maintenance services.
-
D.
hasServiceChief
Indicates that one entity serves as the chief or head responsible for overseeing the services of another entity.
-
E.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaaee104819085966bc54d5da9c0 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd949c120819099a9d56eb71a0339 |
completed | March 7, 2026, 7:52 a.m. |
Created at: March 6, 2026, 9:55 p.m.