Triple
T37607462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 430 Park Avenue |
E935692
|
entity |
| Predicate | hasSecurityDesk |
P22957
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [430 Park Avenue, hasSecurityDesk, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityDesk Context triple: [430 Park Avenue, hasSecurityDesk, true]
-
A.
hasHighSecurityFacility
Indicates that an entity possesses or operates a facility characterized by a high level of security measures and protections.
-
B.
hasSecurityTeam
Indicates that an entity is supported or protected by a designated security team responsible for its safety or security operations.
-
C.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
-
D.
hasSecurityPresence
chosen
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
E.
hasSecurityInstitution
Indicates that an entity is associated with, governed by, or protected through a particular security-related institution or organization.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a008e29f76881908e656dbbd7fceea3 |
completed | May 10, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_6a008dc01b308190bc26e69814692f82 |
completed | May 10, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:18 p.m.