Triple
T26469871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post Office Tower |
E665869
|
entity |
| Predicate | publicAccessSuspended |
P164980
|
FINISHED |
| Object | after 1971 bombing |
—
|
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: after 1971 bombing | Statement: [Post Office Tower, publicAccessSuspended, after 1971 bombing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicAccessSuspended Context triple: [Post Office Tower, publicAccessSuspended, after 1971 bombing]
-
A.
publicAccess
Indicates that something is available for use, entry, or viewing by the general public without special restrictions or permissions.
-
B.
isSuspended
Indicates that an entity is temporarily removed from its normal role, function, or privileges, typically as a result of a rule, policy, or disciplinary action.
-
C.
publicAccessChange
chosen
Indicates a change in whether and how something is accessible to the general public.
-
D.
suspendedIn
Indicates that one entity is held or maintained within another medium or environment without settling or separating.
-
E.
confirmedSuspensionOf
Indicates that one entity has officially acknowledged and validated the suspension or temporary halt of another 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 12:18 a.m.