Triple
T26436610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacMurray College |
E664965
|
entity |
| Predicate | hadResidentialComponent |
P9064
|
FINISHED |
| Object | residential campus |
—
|
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: residential campus | Statement: [MacMurray College, hadResidentialComponent, residential campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadResidentialComponent Context triple: [MacMurray College, hadResidentialComponent, residential campus]
-
A.
hasResidentialBuilding
Indicates that an entity possesses, contains, or is associated with a residential building as part of its properties or components.
-
B.
hasResidentialArea
chosen
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
C.
hasResidenceFeature
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
D.
isResidentialUnitOf
Indicates that a specific residential unit (e.g., apartment, house) belongs to or is part of a larger property, building, or complex.
-
E.
hasResidentialBuildingsType
Indicates that an entity is associated with a specific type or category of residential buildings.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61217c7dc8190bd76149fba4fce97 |
completed | May 2, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:54 p.m.