Triple
T33132320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carman Hall |
E847906
|
entity |
| Predicate | hasResidentAdvisers |
P204216
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Carman Hall, hasResidentAdvisers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentAdvisers Context triple: [Carman Hall, hasResidentAdvisers, yes]
-
A.
coResident
Indicates that two or more entities live in the same residence or dwelling at the same time.
-
B.
hasTypicalResident
Indicates that an entity characteristically or commonly has a particular type of resident associated with it.
-
C.
hasResidentArtist
Indicates that one entity serves as the resident artist associated with or based at another entity.
-
D.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
-
E.
hasResidency
Indicates that an entity holds an official, legally recognized residential status in a particular place or jurisdiction.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a034af7066c81908719bff353d77b16 |
completed | May 12, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_6a034a2fc2308190b0b8fbd458a39323 |
completed | May 12, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_6a034af656d88190881820908f6d2958 |
completed | May 12, 2026, 3:44 p.m. |
Created at: May 1, 2026, 1:27 a.m.