Triple
T6883925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United College |
E158867
|
entity |
| Predicate | hasResidenceCapacityFor |
P73935
|
FINISHED |
| Object | 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: students | Statement: [United College, hasResidenceCapacityFor, students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidenceCapacityFor Context triple: [United College, hasResidenceCapacityFor, students]
-
A.
canResideIn
Indicates that an entity is capable of living, staying, or being located within a specified place or environment.
-
B.
hasResidentPopulation
Indicates that a place or administrative area has a population of people who live there permanently or for an extended period.
-
C.
hasResidenceFeature
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
D.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
E.
isResidentialBaseFor
Indicates that a location serves as the primary place of residence or home base for a person or group.
- F. None of above. chosen
Provenance (4 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_69c688342f6c8190ad7eea6ba262db99 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8ea59108190a85f9112b6a4e59a |
completed | March 27, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:23 p.m.