Triple
T7317752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salih |
E168456
|
entity |
| Predicate | survivedWith |
P34422
|
FINISHED |
| Object | those who believed |
—
|
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: those who believed | Statement: [Salih, survivedWith, those who believed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivedWith Context triple: [Salih, survivedWith, those who believed]
-
A.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
B.
survivorWith
chosen
Indicates a relationship where one entity survives an event or condition together with, or in the presence of, another entity.
-
C.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
-
D.
survivedEvent
Indicates that an entity continued to live or exist after experiencing and not being destroyed or killed by a particular event.
-
E.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef178b3081908cd0c62466069741 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.