Triple
T19177652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overlords |
E469479
|
entity |
| Predicate | policyOnVisibility |
P125239
|
FINISHED |
| Object | initially conceal physical appearance |
—
|
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: initially conceal physical appearance | Statement: [Overlords, policyOnVisibility, initially conceal physical appearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyOnVisibility Context triple: [Overlords, policyOnVisibility, initially conceal physical appearance]
-
A.
viewOnPolicy
Indicates a stance, opinion, or perspective that an entity holds regarding a specific policy.
-
B.
policyRestriction
chosen
Indicates that an entity is subject to a limiting rule, condition, or constraint imposed by a policy.
-
C.
visibilityReason
Indicates the reason or cause for why something is visible or has become visible in a given context.
-
D.
visibilityRequirement
Indicates that one entity must be visible or perceivable under specified conditions for another entity, action, or rule to apply.
-
E.
visibilityStatus
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f618f18c8190b98995fda4b6fea0 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.