Triple
T323452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheremetyevo International Airport |
E6463
|
entity |
| Predicate | hasSecurityType |
P3487
|
FINISHED |
| Object | civilian |
—
|
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: civilian | Statement: [Sheremetyevo International Airport, hasSecurityType, civilian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityType Context triple: [Sheremetyevo International Airport, hasSecurityType, civilian]
-
A.
securityType
chosen
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
B.
hasSecuritySupport
Indicates that one entity provides security-related assistance, maintenance, or protection services for another entity.
-
C.
hasSecurityArchitecture
Indicates that an entity is associated with or defined by a particular security architecture design or framework.
-
D.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
-
E.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea82ba748190bae651f5de908617 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.