Triple
T9973733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wessex Lane Halls |
E196271
|
entity |
| Predicate | typicalResidentType |
P62073
|
FINISHED |
| Object | undergraduate students |
—
|
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: undergraduate students | Statement: [Wessex Lane Halls, typicalResidentType, undergraduate students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalResidentType Context triple: [Wessex Lane Halls, typicalResidentType, undergraduate students]
-
A.
typicalConstituentType
Indicates the usual or characteristic type of component that typically makes up or forms part of something.
-
B.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
C.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
D.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
-
E.
typicalGroup
chosen
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7bc68608190a6545ea112850618 |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.