Triple
T5806972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonah |
E128768
|
entity |
| Predicate | thenObeyedCommand |
P66633
|
FINISHED |
| Object | went to Nineveh |
—
|
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: went to Nineveh | Statement: [Jonah, thenObeyedCommand, went to Nineveh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thenObeyedCommand Context triple: [Jonah, thenObeyedCommand, went to Nineveh]
-
A.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
B.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
C.
coCommandedWith
Indicates that two or more entities shared command authority together over the same unit, operation, or context during a given period.
-
D.
commandedFor
Indicates that one entity issued an order or directive on behalf of, or in service of, another entity or purpose.
-
E.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b15d8108190b434da42631c4e0c |
completed | March 22, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02b10def8819080859bc6505405ed |
completed | March 22, 2026, 5:46 p.m. |
Created at: March 22, 2026, 3:52 p.m.