Triple
T31248706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | לבן הארמי |
E796756
|
entity |
| Predicate | קרוב_משפחה_של |
P28764
|
FINISHED |
| Object | יעקב |
—
|
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: יעקב | Statement: [לבן הארמי, קרוב_משפחה_של, יעקב]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: קרוב_משפחה_של Context triple: [לבן הארמי, קרוב_משפחה_של, יעקב]
-
A.
familyOf
chosen
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
B.
topFamily
Indicates that the subject entity belongs to the highest-ranking or primary family group within a given hierarchy or classification.
-
C.
familyRevealedIn
Indicates that a family or familial relationship becomes known, disclosed, or uncovered within a particular context, situation, or medium.
-
D.
enemyFamily
Indicates that two entities belong to families that are hostile or in conflict with each other.
-
E.
familyFate
Indicates a relationship where the outcome, destiny, or ultimate circumstances of one entity are determined by or closely tied to those of its family or familial group.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:11 p.m.