Triple
T35482126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alayne Stone |
E1025495
|
entity |
| Predicate | maintainsCoverIdentity |
P188459
|
FINISHED |
| Object | inPresenceOfValeLords |
—
|
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: inPresenceOfValeLords | Statement: [Alayne Stone, maintainsCoverIdentity, inPresenceOfValeLords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsCoverIdentity Context triple: [Alayne Stone, maintainsCoverIdentity, inPresenceOfValeLords]
-
A.
maintainsCoverAs
chosen
Indicates that one entity continues to uphold or preserve a deceptive or protective disguise, identity, or role in relation to another entity.
-
B.
identityConcealedBy
Indicates that one entity hides, masks, or obscures the true identity of another entity.
-
C.
homeLocationInCoverIdentity
Indicates that an entity’s home location is specified within the context of its cover (false or assumed) identity.
-
D.
characterCoverIdentity
Indicates that one character uses another identity as a cover or disguise, typically concealing their true identity.
-
E.
identityRetainedIn
Indicates that an entity preserves its essential identity or continuity across a change, transformation, or over time.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:04 p.m.