Triple
T30606284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potifar |
E779052
|
entity |
| Predicate | entrustedHouseholdTo |
P96404
|
FINISHED |
| Object | Joseph |
—
|
NE NERFINISHED |
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: Joseph | Statement: [Potifar, entrustedHouseholdTo, Joseph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entrustedHouseholdTo Context triple: [Potifar, entrustedHouseholdTo, Joseph]
-
A.
entrustedTo
chosen
Indicates that responsibility, care, or control of something has been formally given by one party to another.
-
B.
entrustsChildTo
Indicates that one person or entity places a child under the care, supervision, or responsibility of another person or entity.
-
C.
intendedToHouse
Indicates that one entity is designed or meant to serve as a dwelling or accommodation space for another entity.
-
D.
heldInTrustFor
Indicates that one party holds an asset, right, or interest on behalf of and for the benefit of another party, subject to fiduciary or trust obligations.
-
E.
takesIntoHouse
Indicates that one entity brings or leads another entity into a house or dwelling.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:25 p.m.