Triple
T13378671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Put |
E319256
|
entity |
| Predicate | roleInJeremiah46 |
P109683
|
FINISHED |
| Object | warriors supporting Egypt |
—
|
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: warriors supporting Egypt | Statement: [Put, roleInJeremiah46, warriors supporting Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInJeremiah46 Context triple: [Put, roleInJeremiah46, warriors supporting Egypt]
-
A.
roleDuringMaccabeanRevolt
Indicates the specific role or function an entity held or performed during the period of the Maccabean Revolt.
-
B.
roleAtKarbala
Indicates the specific role, position, or function an entity held in relation to the events of the Battle of Karbala.
-
C.
roleInExodusTradition
Indicates having a specific function, status, or significance within the narratives, practices, or interpretations associated with the Exodus tradition.
-
D.
hasRoleInAncientMesopotamia
Indicates that an entity held a specific social, political, religious, or occupational role within the context of ancient Mesopotamian society.
-
E.
roleInIsrael
Indicates that an entity holds or held a specific role, position, or function within the context of Israel.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce56c6c8190adf4e19f6d1bc233 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:33 p.m.