Triple
T30646806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Campus |
E780145
|
entity |
| Predicate | hasServiceUse |
P166595
|
FINISHED |
| Object | student support services |
—
|
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: student support services | Statement: [South Campus, hasServiceUse, student support services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceUse Context triple: [South Campus, hasServiceUse, student support services]
-
A.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
B.
serviceUse
chosen
Indicates that one entity makes use of, accesses, or consumes a service provided by another entity.
-
C.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
D.
hasServiceTime
Indicates that an entity is associated with a specific duration or schedule during which a service is provided.
-
E.
hasHistoricalUsageIn
Indicates that something has been used or practiced within a particular historical period, context, or tradition.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: April 29, 2026, 8:29 p.m.