Triple
T24914265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daejeon campus |
E623932
|
entity |
| Predicate | hasStudentAccommodationType |
P108081
|
FINISHED |
| Object | on-campus dormitories |
—
|
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: on-campus dormitories | Statement: [Daejeon campus, hasStudentAccommodationType, on-campus dormitories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentAccommodationType Context triple: [Daejeon campus, hasStudentAccommodationType, on-campus dormitories]
-
A.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
B.
hasDormitorySystem
chosen
Indicates that an institution operates or is associated with a system of dormitories for housing residents.
-
C.
hasLodgeType
Indicates that an entity is associated with or classified by a particular type or category of lodge.
-
D.
hasStudentHousingNearby
Indicates that suitable student housing options are located close to the referenced entity.
-
E.
hasStudentHousingCooperationWith
Indicates that one institution collaborates with another to provide or manage student housing or accommodation services.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 5:28 a.m.