Triple
T5830688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuck School of Business |
E129336
|
entity |
| Predicate | residentialModel |
P53125
|
FINISHED |
| Object | campus-based |
—
|
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: campus-based | Statement: [Tuck School of Business, residentialModel, campus-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residentialModel Context triple: [Tuck School of Business, residentialModel, campus-based]
-
A.
residentialSystem
chosen
Indicates a system, structure, or arrangement that is specifically designed for, associated with, or functioning within residential living environments.
-
B.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
C.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
D.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
E.
houses
Indicates that one entity serves as a dwelling or shelter for another entity.
- 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.