Triple
T27617730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abimelech |
E700483
|
entity |
| Predicate | takesIntoHouse |
P162753
|
FINISHED |
| Object | Sarah |
—
|
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: Sarah | Statement: [Abimelech, takesIntoHouse, Sarah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesIntoHouse Context triple: [Abimelech, takesIntoHouse, Sarah]
-
A.
intendedToHouse
Indicates that one entity is designed or meant to serve as a dwelling or accommodation space for another entity.
-
B.
usedToHouse
Indicates that something previously served as a dwelling or shelter for someone or something, but no longer does so.
-
C.
alsoLaidInHouse
Indicates that the same entity was additionally laid or deposited within a house or dwelling, in relation to another laying event.
-
D.
household
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
E.
usedByHouse
Indicates that something is utilized or employed by a particular house.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f630d9c4ec8190af57c75c41ac5b05 |
completed | May 2, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:13 p.m.