Triple
T28494086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Drake Building |
E721055
|
entity |
| Predicate | hasSecurePerimeter |
P18602
|
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: [Edward Drake Building, hasSecurePerimeter, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurePerimeter Context triple: [Edward Drake Building, hasSecurePerimeter, yes]
-
A.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
B.
hasSecurityRegion
Indicates that an entity is associated with, governed by, or falls within a specific security region or security-related jurisdiction.
-
C.
hasSecurityArea
chosen
Indicates that an entity is associated with, assigned to, or falls within a defined security-controlled area or zone.
-
D.
hasSecureCommunications
Indicates that one entity maintains protected, confidential, and tamper-resistant channels for exchanging information with another entity.
-
E.
hasSecurityDimension
Indicates that something possesses or is associated with a particular aspect or dimension of security.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 28, 2026, 3:03 a.m.