Triple
T4904758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathan |
E109886
|
entity |
| Predicate | familyRelationToDavid |
P38921
|
FINISHED |
| Object | not a blood relative in the biblical text |
—
|
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: not a blood relative in the biblical text | Statement: [Nathan, familyRelationToDavid, not a blood relative in the biblical text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRelationToDavid Context triple: [Nathan, familyRelationToDavid, not a blood relative in the biblical text]
-
A.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
B.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
D.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
E.
relationshipToCharacter
chosen
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.