Triple
T15706914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyberman city |
E380735
|
entity |
| Predicate | hasSecuritySystem |
P2368
|
FINISHED |
| Object | automated Cyberman defenses |
—
|
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: automated Cyberman defenses | Statement: [Cyberman city, hasSecuritySystem, automated Cyberman defenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecuritySystem Context triple: [Cyberman city, hasSecuritySystem, automated Cyberman defenses]
-
A.
hasDoorGuard
Indicates that an entity has another entity serving as a guard for its door or entrance.
-
B.
securityApparatusControl
Indicates that one entity exercises authority over, manages, or directs the operations and decisions of a security or law-enforcement apparatus.
-
C.
securityFeature
chosen
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.
doorSafety
Indicates that a door meets specified safety conditions or standards, such as being secure, unobstructed, and compliant with safety regulations.
-
E.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.