Triple
T16904017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indy Hall, University of Ibadan |
E424509
|
entity |
| Predicate | studentCommunity |
P5612
|
FINISHED |
| Object | hall residents |
—
|
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: hall residents | Statement: [Indy Hall, University of Ibadan, studentCommunity, hall residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentCommunity Context triple: [Indy Hall, University of Ibadan, studentCommunity, hall residents]
-
A.
campusLife
Indicates the overall experience, activities, and social environment associated with being part of a particular campus or educational institution.
-
B.
studentComponent
Indicates that one entity functions as a student-related part, module, or subunit within a larger system, structure, or context.
-
C.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
D.
studentsWing
chosen
Indicates a relationship where a particular wing, section, or area is designated for or associated with students.
-
E.
studentSupport
Indicates that one entity provides academic, emotional, or practical assistance to another in an educational context.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8de3070819085bfe9696bc887ea |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.