Triple
T30226160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piazza Cavour (Foggia) |
E768484
|
entity |
| Predicate | hasSafetyProvision |
P63490
|
FINISHED |
| Object | public lighting |
—
|
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: public lighting | Statement: [Piazza Cavour (Foggia), hasSafetyProvision, public lighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyProvision Context triple: [Piazza Cavour (Foggia), hasSafetyProvision, public lighting]
-
A.
hasSecurityClause
Indicates that an agreement, contract, or document includes a provision specifying security-related requirements, protections, or safeguards.
-
B.
hasSafetyCharacteristic
chosen
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
-
C.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
D.
hasSafetyInformation
Indicates that one entity provides or is associated with safety-related details, warnings, or guidelines about another entity.
-
E.
hasSafetyCertificate
Indicates that an entity possesses or has been granted a valid safety certificate.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 7:36 p.m.