Triple
T16403986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heyendaal campus |
E398375
|
entity |
| Predicate | hasStudentHousingNearby |
P123293
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Heyendaal campus, hasStudentHousingNearby, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentHousingNearby Context triple: [Heyendaal campus, hasStudentHousingNearby, yes]
-
A.
hasHousingArrangement
Indicates that an entity has a specific type or status of housing or living arrangement in relation to another entity or context.
-
B.
hasStudentHousingCooperationWith
Indicates that one institution collaborates with another to provide or manage student housing or accommodation services.
-
C.
hasHousingAccess
Indicates that an entity has the ability, right, or opportunity to obtain or use suitable housing.
-
D.
hasNearbyInstitution
Indicates that one entity is located close to or in the immediate vicinity of an institution.
-
E.
hasNearbyHotel
Indicates that one entity is located close to or within a short distance of a hotel.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d12dc08190a5b497692b667ed7 |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.