Triple
T24948804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shawfair new town |
E624266
|
entity |
| Predicate | hasFeaturePlanned |
P134005
|
FINISHED |
| Object | community facilities |
—
|
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: community facilities | Statement: [Shawfair new town, hasFeaturePlanned, community facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeaturePlanned Context triple: [Shawfair new town, hasFeaturePlanned, community facilities]
-
A.
plannedCapability
Indicates that an entity is intended or scheduled to possess or provide a particular capability in the future.
-
B.
hasPlanningCharacteristic
Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
-
C.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
D.
hasPlanningFunction
Indicates that an entity is responsible for or involved in planning, organizing, or determining future actions or strategies.
-
E.
hasPlannedPart
chosen
Indicates that one entity includes another entity as a component or segment within a planned or scheduled whole.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:55 a.m.