Triple
T27178357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oranjemund |
E683115
|
entity |
| Predicate | hasRestrictedAccessHistory |
P40119
|
FINISHED |
| Object | diamond security zone |
—
|
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: diamond security zone | Statement: [Oranjemund, hasRestrictedAccessHistory, diamond security zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestrictedAccessHistory Context triple: [Oranjemund, hasRestrictedAccessHistory, diamond security zone]
-
A.
hasAccessRestrictionHistory
chosen
Indicates that there exists a record or sequence of past changes detailing how access to something has been restricted over time.
-
B.
accessRestrictedSince
Indicates that access to an entity has been limited or blocked starting from a specified point in time.
-
C.
hasPublicAccessRestrictions
Indicates that there are specific limitations or conditions governing public access to the associated resource or entity.
-
D.
hasDisabledAccess
Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
-
E.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 27, 2026, 9:27 a.m.