Triple
T519453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacob |
E10780
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Joseph |
E67279
|
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: Joseph | Statement: [Jacob, father, Joseph]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Joseph Context triple: [Jacob, father, Joseph]
-
A.
Joseph
Joseph is the first name of J. C. R. Licklider, a pioneering computer scientist often regarded as a key figure in the development of the internet and interactive computing.
-
B.
Joseph
Joseph is the husband of Mary in the New Testament and the earthly guardian of Jesus, venerated in Christianity as a model of humility, obedience, and fatherhood.
-
C.
Jacob
Jacob is a central patriarch in the Hebrew Bible, regarded in Judaism as the father of the twelve tribes of Israel.
-
D.
Simeon
chosen
Simeon is a biblical figure, one of the twelve sons of Jacob and a progenitor of one of the tribes of Israel.
-
E.
Samuel
Samuel is a masculine given name of Hebrew origin meaning "name of God" or "God has heard," widely used across many cultures and languages.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1a00a6c8190a62dc7c901c2f2ff |
completed | Feb. 28, 2026, 1:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4cc5868d88190bb0b107fb820aafe |
completed | March 1, 2026, 11:31 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.