Triple
T10863238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manor Park campus |
E256459
|
entity |
| Predicate | hasResidentialCapacityFor |
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: [Manor Park campus, hasResidentialCapacityFor, students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentialCapacityFor Context triple: [Manor Park campus, hasResidentialCapacityFor, students]
-
A.
hasResidenceCapacityFor
chosen
Indicates that an entity’s residence can accommodate or provide living space for a specified number or type of occupants.
-
B.
isResidentialBaseFor
Indicates that a location serves as the primary place of residence or home base for a person or group.
-
C.
typicalHomeCapacity
Indicates the usual or standard number of occupants that a home is designed or expected to accommodate.
-
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.
hasResidentialArea
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75152f93081909a8186bab5efaf97 |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.