Triple
T19637084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Yasa |
E471424
|
entity |
| Predicate | continuedMissionOf |
P136783
|
FINISHED |
| Object | earlier prophets |
—
|
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: earlier prophets | Statement: [Al-Yasa, continuedMissionOf, earlier prophets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedMissionOf Context triple: [Al-Yasa, continuedMissionOf, earlier prophets]
-
A.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
B.
segmentMission
Indicates that a specific mission is associated with, assigned to, or carried out within a particular segment or phase.
-
C.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
-
D.
maintainedMissionIn
Indicates that an entity continued to operate or uphold a mission within a specified location or context.
-
E.
missionTo
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64107f3fc8190ace6ae67287d280c |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.