Triple
T4621149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyde Park Firehouse |
E100986
|
entity |
| Predicate | hasLocalImportance |
P1887
|
FINISHED |
| Object | Hyde Park community |
—
|
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: Hyde Park community | Statement: [Hyde Park Firehouse, hasLocalImportance, Hyde Park community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalImportance Context triple: [Hyde Park Firehouse, hasLocalImportance, Hyde Park community]
-
A.
relativeImportanceInCountry
Indicates the comparative significance or priority of something within the context of a specific country.
-
B.
isImportantFor
chosen
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
C.
hasLocalLevel
Indicates that one entity possesses, is associated with, or is defined at a specific local administrative or organizational level relative to another entity.
-
D.
isLocalLandmark
Indicates that something is recognized as a notable or significant landmark within a specific local area or community.
-
E.
isGloballySignificant
Indicates that something has importance, impact, or relevance on a worldwide scale rather than being limited to a local or regional context.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e560f481908abb1a97b4ff5795 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.