Triple
T187256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Campus |
E4007
|
entity |
| Predicate | primaryResidents |
P2750
|
FINISHED |
| Object | Yale College first-year 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: Yale College first-year students | Statement: [Old Campus, primaryResidents, Yale College first-year students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryResidents Context triple: [Old Campus, primaryResidents, Yale College first-year students]
-
A.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
B.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
C.
populationIncludes
chosen
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
D.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
-
E.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2594940e48190a3d8efbce46241c3 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25670feb081908e26a2543ebe7b3a |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.