Triple
T28707811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SBASE |
E729742
|
entity |
| Predicate | appliesSafetyStandardsTo |
P136038
|
FINISHED |
| Object | Buenos Aires Underground |
—
|
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: Buenos Aires Underground | Statement: [SBASE, appliesSafetyStandardsTo, Buenos Aires Underground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesSafetyStandardsTo Context triple: [SBASE, appliesSafetyStandardsTo, Buenos Aires Underground]
-
A.
safetyStandardsSimilarTo
Indicates that two entities have safety standards that are comparable or closely aligned in their requirements or rigor.
-
B.
safetyStandardLevel
Indicates the degree or tier of safety requirements or protections that apply to an entity or activity.
-
C.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
D.
standardsUsedIn
chosen
Indicates that certain standards are applied, referenced, or followed within a particular context, process, or entity.
-
E.
hasReliabilityStandards
Indicates that one entity defines, follows, or is governed by specific reliability standards established 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 28, 2026, 5:46 a.m.