Triple
T26874077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khidr |
E676695
|
entity |
| Predicate | believedBySomeToBe |
P159732
|
FINISHED |
| Object | immortal |
—
|
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: immortal | Statement: [Khidr, believedBySomeToBe, immortal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedBySomeToBe Context triple: [Khidr, believedBySomeToBe, immortal]
-
A.
believedBy
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
-
B.
believedToHave
chosen
Indicates that one entity is thought or assumed, but not confirmed, to possess or exhibit another entity or property.
-
C.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
D.
believedProvidedBy
Indicates that something is thought or assumed to have been supplied or made available by a particular source or provider.
-
E.
traditionallyBelievedToHaveKnown
Indicates that, according to tradition or customary belief, one entity was thought to have known or been aware of another entity or some information.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 5:34 a.m.