Triple
T11949235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block Z |
E284384
|
entity |
| Predicate | safetyStatusAtTime |
P11824
|
FINISHED |
| Object | inadequate crowd segregation |
—
|
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: inadequate crowd segregation | Statement: [Block Z, safetyStatusAtTime, inadequate crowd segregation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyStatusAtTime Context triple: [Block Z, safetyStatusAtTime, inadequate crowd segregation]
-
A.
statusAtTime
Indicates that an entity has a particular status or condition at a specified point in time.
-
B.
statusAtDay
Indicates the specific status or condition an entity has on a given calendar day.
-
C.
hasPedestrianStatusSince
Indicates that an entity has held a particular pedestrian-related status continuously starting from a specified point in time.
-
D.
legalStatusDuringEvent
Indicates the legal status or condition an entity holds specifically during the time period of a given event.
-
E.
securityStatus
chosen
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90346825c8190ab4482a1fc8eed56 |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.