Triple
T31696907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokdim |
E808940
|
entity |
| Predicate | hasSecurityFence |
P14204
|
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: [Nokdim, hasSecurityFence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityFence Context triple: [Nokdim, hasSecurityFence, yes]
-
A.
hasDoorGuard
Indicates that an entity has another entity serving as a guard for its door or entrance.
-
B.
hasBorderWallOrFence
chosen
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
-
C.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
-
D.
hasGuardBars
Indicates that one entity is equipped with or protected by guard bars installed on or around it.
-
E.
houseEntranceSecurity
Indicates the security measures or controls in place at the entrance of a house to regulate or monitor access.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: April 30, 2026, 11:10 p.m.