Triple
T19972386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Erin Lifeboat Station |
E480109
|
entity |
| Predicate | followsSafetyStandards |
P17338
|
FINISHED |
| Object | RNLI operational standards |
—
|
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: RNLI operational standards | Statement: [Port Erin Lifeboat Station, followsSafetyStandards, RNLI operational standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsSafetyStandards Context triple: [Port Erin Lifeboat Station, followsSafetyStandards, RNLI operational standards]
-
A.
safetyStandardsSimilarTo
Indicates that two entities have safety standards that are comparable or closely aligned in their requirements or rigor.
-
B.
hasSafetyRegulationCompliance
chosen
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
C.
followsClinicalStandardsOf
Indicates that one entity adheres to, complies with, or is guided by the clinical standards, protocols, or guidelines established by another entity.
-
D.
hasReliabilityStandards
Indicates that one entity defines, follows, or is governed by specific reliability standards established by another entity.
-
E.
standardsUsedIn
Indicates that certain standards are applied, referenced, or followed within a particular context, process, or 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bca94c0819095c902a411c4c4b8 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.