Triple
T22454774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost City |
E555085
|
entity |
| Predicate | safetyStandardsFollowed |
P136038
|
FINISHED |
| Object | Indonesian amusement ride regulations |
—
|
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: Indonesian amusement ride regulations | Statement: [Lost City, safetyStandardsFollowed, Indonesian amusement ride regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyStandardsFollowed Context triple: [Lost City, safetyStandardsFollowed, Indonesian amusement ride regulations]
-
A.
safetyStandardsSimilarTo
Indicates that two entities have safety standards that are comparable or closely aligned in their requirements or rigor.
-
B.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
C.
hasReliabilityStandards
Indicates that one entity defines, follows, or is governed by specific reliability standards established by another entity.
-
D.
standardsUsedIn
chosen
Indicates that certain standards are applied, referenced, or followed within a particular context, process, or entity.
-
E.
hasSecurityStandard
Indicates that an entity complies with, follows, or is governed by a specified security standard or framework.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4e2bd4819083e5bed44e9776c6 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.