Triple
T31669676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qaʼim |
E808235
|
entity |
| Predicate | expectedBy |
P172616
|
FINISHED |
| Object | believers across generations |
—
|
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: believers across generations | Statement: [Qaʼim, expectedBy, believers across generations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedBy Context triple: [Qaʼim, expectedBy, believers across generations]
-
A.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
B.
expectedValue
Indicates the predicted or average outcome of a variable or event, typically computed as a probability-weighted sum of all possible values.
-
C.
hasTemporalExpectation
Indicates that one entity holds an expectation about when (in time) another event, state, or action will occur or be valid.
-
D.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
-
E.
heldUntil
Indicates that a state, condition, or action continues to hold true up to a specified time or event, and may cease to hold immediately after that point.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 30, 2026, 11 p.m.