Triple
T34643448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ally Andrews |
E889631
|
entity |
| Predicate | survivalAdvantage |
P180107
|
FINISHED |
| Object | accustomed to silence |
—
|
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: accustomed to silence | Statement: [Ally Andrews, survivalAdvantage, accustomed to silence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivalAdvantage Context triple: [Ally Andrews, survivalAdvantage, accustomed to silence]
-
A.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
B.
survivalAttributedTo
Indicates that an entity’s continued existence or survival is credited to, or causally linked with, another entity or factor.
-
C.
survivesWith
Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
-
D.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
E.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
- F. None of above. chosen
Provenance (4 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f731cc6d1881908f80386ef4d70a09 |
completed | May 3, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69f7317779e08190bf85777578221a6b |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f731cbca10819091eefe2f2487928e |
completed | May 3, 2026, 11:30 a.m. |
Created at: May 1, 2026, 2:04 a.m.