Triple
T8324698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilston |
E194920
|
entity |
| Predicate | hasPlannedHousingCapacity |
P31309
|
FINISHED |
| Object | thousands of new homes (garden town concept) |
—
|
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: thousands of new homes (garden town concept) | Statement: [Gilston, hasPlannedHousingCapacity, thousands of new homes (garden town concept)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedHousingCapacity Context triple: [Gilston, hasPlannedHousingCapacity, thousands of new homes (garden town concept)]
-
A.
hasResidenceCapacityFor
Indicates that an entity’s residence can accommodate or provide living space for a specified number or type of occupants.
-
B.
hasPlannedCommunity
Indicates that an entity is associated with or contains a community that has been intentionally designed and organized according to a specific development plan.
-
C.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
D.
hasHousingUnits
chosen
Indicates that an entity possesses or contains a specified number or set of housing units.
-
E.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f7e4f8081908e0f876ad962c932 |
completed | March 31, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.