Triple
T24825237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divine Revelation |
E621167
|
entity |
| Predicate | isWitnessedBy |
P9232
|
FINISHED |
| Object | the 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: the prophets | Statement: [Divine Revelation, isWitnessedBy, the prophets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWitnessedBy Context triple: [Divine Revelation, isWitnessedBy, the prophets]
-
A.
hasWitnessType
Indicates that an event, incident, or situation is associated with a specific category or type of witness involved.
-
B.
hasPrimaryWitness
Indicates that an entity is the main or principal witness associated with another entity or event.
-
C.
notableWitness
chosen
Indicates that one entity is a significant or prominent witness to an event, action, or situation involving another entity.
-
D.
canCallAsWitness
Indicates that one party is permitted or eligible to summon another party to provide testimony as a witness in a proceeding.
-
E.
socialWitness
Indicates that one entity observes, attends, or is present for another entity’s social interaction or socially significant event.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:05 a.m.