Triple
T35096511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Chambers |
E1012879
|
entity |
| Predicate | isInDistrictType |
P176124
|
FINISHED |
| Object | central business district |
—
|
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: central business district | Statement: [Law Chambers, isInDistrictType, central business district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInDistrictType Context triple: [Law Chambers, isInDistrictType, central business district]
-
A.
withinDistrictType
chosen
Indicates that one entity is located inside or falls under the jurisdiction of a specific type or category of district.
-
B.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
C.
appliesToDistrict
Indicates that something (such as a rule, policy, or condition) is relevant or applicable to a specific district.
-
D.
isKeyDistrictOf
Indicates that a district holds strategic, political, or administrative importance within a larger region, organization, or system.
-
E.
isInNeighborhoodType
Indicates that one entity is located within, or belongs to, a specific category or type of neighborhood defined by the other entity.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.