Triple
T37470325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbiter’s Chamber |
E931135
|
entity |
| Predicate | securityLevelInUniverse |
P61556
|
FINISHED |
| Object | highly restricted area in Oribos |
—
|
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: highly restricted area in Oribos | Statement: [Arbiter’s Chamber, securityLevelInUniverse, highly restricted area in Oribos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityLevelInUniverse Context triple: [Arbiter’s Chamber, securityLevelInUniverse, highly restricted area in Oribos]
-
A.
securityLevelDetail
Indicates the specific classification or degree of security associated with an entity, often including nuanced or descriptive information about its protection level.
-
B.
securityLevelsInclude
Indicates that one entity’s defined security levels contain or encompass the security levels of another entity.
-
C.
encryptionLevel
Indicates the degree or strength of cryptographic protection applied to data or communications.
-
D.
typicalSecurityLevel
Indicates the usual or standard security level that is generally applied or expected in a given context or system.
-
E.
fictionalSecurityLevel
chosen
Indicates the degree or category of security status assigned within a fictional or imagined context.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:17 p.m.