Triple
T11953945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokolinaya Gora MCC station |
E284499
|
entity |
| Predicate | hasSecurityChecks |
P22957
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sokolinaya Gora MCC station, hasSecurityChecks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityChecks Context triple: [Sokolinaya Gora MCC station, hasSecurityChecks, yes]
-
A.
hasSecurityPresence
chosen
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
B.
hasSecurityFunction
Indicates that an entity performs, provides, or is responsible for a security-related role, protection mechanism, or safeguarding function for another entity or system.
-
C.
hasSecuritySupport
Indicates that one entity provides security-related assistance, maintenance, or protection services for another entity.
-
D.
hasSecurityDimension
Indicates that something possesses or is associated with a particular aspect or dimension of security.
-
E.
hasSecurityClause
Indicates that an agreement, contract, or document includes a provision specifying security-related requirements, protections, or safeguards.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90365da288190a132703df563de23 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.