Triple
T5373287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delilah |
E108901
|
entity |
| Predicate | bribedBy |
P63614
|
FINISHED |
| Object | Philistine rulers |
—
|
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: Philistine rulers | Statement: [Delilah, bribedBy, Philistine rulers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bribedBy Context triple: [Delilah, bribedBy, Philistine rulers]
-
A.
withdrewInFavorOf
Indicates that one party retracted or gave up its position, claim, or candidacy in support of another party.
-
B.
pledgedByOthers
Indicates that a commitment, promise, or pledge toward an entity is made by parties other than the primary or focal entity.
-
C.
brokeredBy
Indicates that an intermediary agent or organization arranged, facilitated, or negotiated the relationship, transaction, or agreement between the involved entities.
-
D.
blackmailedFor
Indicates that one entity coerces another into doing or not doing something by threatening to reveal damaging or sensitive information about them.
-
E.
bounty
Indicates that a reward or payment is offered for performing a specific action or achieving a particular outcome related to an entity.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd887f5b0081909456992d1a071928 |
completed | March 20, 2026, 5:48 p.m. |
Created at: March 20, 2026, 2:03 p.m.