Triple
T15834513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skydome |
E383951
|
entity |
| Predicate | hasSafetyImprovement |
P33946
|
FINISHED |
| Object | geotechnical monitoring after sinkhole |
—
|
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: geotechnical monitoring after sinkhole | Statement: [Skydome, hasSafetyImprovement, geotechnical monitoring after sinkhole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyImprovement Context triple: [Skydome, hasSafetyImprovement, geotechnical monitoring after sinkhole]
-
A.
safetyChangesImplemented
chosen
Indicates that specific safety-related modifications or measures have been put into effect.
-
B.
hasSafetyCharacteristic
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
-
C.
safetyRecordChangedAfter
Indicates that an entity’s safety record was modified following a specified event, time, or condition.
-
D.
hasLightingImprovements
Indicates that an entity has enhancements or upgrades made to its lighting conditions or systems.
-
E.
safetyBenefit
Indicates that one entity provides, contributes to, or results in an improvement in the safety or risk reduction experienced by 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e673e08819080c3f55a225607c7 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.