Triple
T5889787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mo Mowlam Children’s Park |
E130957
|
entity |
| Predicate | hasSafetyDesign |
P63490
|
FINISHED |
| Object | child-friendly |
—
|
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: child-friendly | Statement: [Mo Mowlam Children’s Park, hasSafetyDesign, child-friendly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyDesign Context triple: [Mo Mowlam Children’s Park, hasSafetyDesign, child-friendly]
-
A.
hasSafetyCharacteristic
chosen
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
-
B.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
C.
hasSafetyCertificate
Indicates that an entity possesses or has been granted a valid safety certificate.
-
D.
safetyRequirement
Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
-
E.
hasSafetyInfrastructure
Indicates that appropriate safety-related structures, systems, or measures are present for the referenced entity or environment.
- 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_69c0085628dc8190b334c1b44c067efc |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.