Triple
T36931044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Abraham |
E913480
|
entity |
| Predicate | includesRelativeHouse |
P205644
|
FINISHED |
| Object | House of Nahor |
E913480
|
NE 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: House of Nahor | Statement: [House of Abraham, includesRelativeHouse, House of Nahor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRelativeHouse Context triple: [House of Abraham, includesRelativeHouse, House of Nahor]
-
A.
hasHouseWithin
Indicates that one entity possesses or is associated with a house that is located within the spatial or administrative boundaries of another entity.
-
B.
includesResidence
Indicates that one entity encompasses, contains, or has within it the residence or dwelling place of another entity.
-
C.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
D.
includesEarlyRelativesOf
Indicates that the subject set or group contains members who are early or ancestral relatives of the entities in the object set or group.
-
E.
relationshipBetweenHouses
Indicates a relational connection or association that exists between two or more houses.
- F. None of above. chosen
Provenance (5 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e1639a5988190b44b9e33c4dd2f00 |
completed | June 26, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.