Triple
T35830751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirisfal Council |
E1035789
|
entity |
| Predicate | guardedSecret |
P110221
|
FINISHED |
| Object | true nature and origin of the Guardian’s power |
—
|
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: true nature and origin of the Guardian’s power | Statement: [Tirisfal Council, guardedSecret, true nature and origin of the Guardian’s power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedSecret Context triple: [Tirisfal Council, guardedSecret, true nature and origin of the Guardian’s power]
-
A.
guardedSecretBy
chosen
Indicates that a secret is being protected or kept confidential by a specific entity.
-
B.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
C.
guardedIn
Indicates that one entity is protected or kept under watch within the bounds or premises of another entity.
-
D.
secretedBy
Indicates that a substance or product is released or produced by a particular cell, tissue, organ, or organism.
-
E.
secretDetail
Indicates that one entity reveals or contains confidential or hidden information about another entity or situation.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.