Triple
T30416287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the LORD |
E773765
|
entity |
| Predicate | speaksThrough |
P97645
|
FINISHED |
| Object | 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: prophets | Statement: [the LORD, speaksThrough, prophets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speaksThrough Context triple: [the LORD, speaksThrough, prophets]
-
A.
speaksWith
Indicates that one entity engages in spoken communication or conversation with another entity.
-
B.
givesSpeechTo
Indicates that one entity delivers a speech or formal address directed toward another entity or audience.
-
C.
givesSpeechIn
Indicates that an entity delivers or presents a speech within a particular location, event, or context.
-
D.
alsoSpeak
Indicates that an entity, in addition to another language or mode of communication already mentioned, speaks this additional language or communicates in this additional way.
-
E.
spokeVia
chosen
Indicates that communication or speech occurred through a particular medium, channel, or intermediary.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6864986008190a550cf740ff6f511 |
completed | May 2, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:05 p.m.