Triple
T437562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Visitor Center |
E10042
|
entity |
| Predicate | securityScreeningRequired |
P12800
|
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: [Capitol Visitor Center, securityScreeningRequired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityScreeningRequired Context triple: [Capitol Visitor Center, securityScreeningRequired, yes]
-
A.
securityStatus
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
-
B.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
C.
securityFeature
Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
-
D.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
E.
visitorRequirement
chosen
Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef26bb78819089b3b5dac0330619 |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddb98e081909efcf9f0a955a908 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.