Triple
T30521559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorldSSP300 |
E776704
|
entity |
| Predicate | safetyStandardsAuthority |
P170768
|
FINISHED |
| Object | FIM |
—
|
NE NERFINISHED |
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: FIM | Statement: [WorldSSP300, safetyStandardsAuthority, FIM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyStandardsAuthority Context triple: [WorldSSP300, safetyStandardsAuthority, FIM]
-
A.
safetyStandardsSimilarTo
Indicates that two entities have safety standards that are comparable or closely aligned in their requirements or rigor.
-
B.
regulatoryStandard
Indicates that one entity serves as an official rule, guideline, or benchmark that governs, constrains, or evaluates the behavior, quality, or performance of another entity.
-
C.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
D.
standardsUsedIn
Indicates that certain standards are applied, referenced, or followed within a particular context, process, or entity.
-
E.
technicalRegulationsAuthority
chosen
Indicates that an authority is responsible for establishing, implementing, or overseeing technical regulations governing certain activities, products, or services.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:17 p.m.