Triple
T10449505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moodiesburn |
E246379
|
entity |
| Predicate | hasCouncilHousingAreas |
P12192
|
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: [Moodiesburn, hasCouncilHousingAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCouncilHousingAreas Context triple: [Moodiesburn, hasCouncilHousingAreas, yes]
-
A.
hasPublicHousing
chosen
Indicates that a location or jurisdiction provides or contains government-funded residential housing available to the public.
-
B.
hasPublicHousingAuthority
Indicates that an entity is associated with, governed by, or served by a specific public housing authority.
-
C.
hasCensusAreas
Indicates that an entity is associated with one or more defined census areas used for demographic or statistical purposes.
-
D.
hasHousingPolicy
Indicates that an entity possesses, adopts, or is governed by a specific housing-related policy or set of rules.
-
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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe09af04819083db42f4de4cb0a9 |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:17 p.m.