Triple
T31836693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Campus |
E812691
|
entity |
| Predicate | typicalResidentLevel |
P189337
|
FINISHED |
| Object | first-year undergraduate |
—
|
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: first-year undergraduate | Statement: [North Campus, typicalResidentLevel, first-year undergraduate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalResidentLevel Context triple: [North Campus, typicalResidentLevel, first-year undergraduate]
-
A.
hasTypicalResident
chosen
Indicates that an entity characteristically or commonly has a particular type of resident associated with it.
-
B.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
C.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
D.
typicalLowestLevel
Indicates that something represents the most basic or minimal level that is commonly or normally found within a given context.
-
E.
coResident
Indicates that two or more entities live in the same residence or dwelling at the same time.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:48 p.m.