Triple
T31386935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph the Carpenter |
E800622
|
entity |
| Predicate | subjectRoleOfJoseph |
P182791
|
FINISHED |
| Object | earthly father of Jesus |
—
|
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: earthly father of Jesus | Statement: [Joseph the Carpenter, subjectRoleOfJoseph, earthly father of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectRoleOfJoseph Context triple: [Joseph the Carpenter, subjectRoleOfJoseph, earthly father of Jesus]
-
A.
roleOfPerson
chosen
Indicates that a specific role, function, or position is assigned to or held by a particular person.
-
B.
sonOccupation
Indicates that a specified occupation is the job or professional role held by a person's son.
-
C.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
D.
roleOfJohnWilliamson
Indicates that an entity serves in the role or capacity associated with John Williamson.
-
E.
roleInHistoryOf
Indicates that one entity holds a specific role, contribution, or significance within the historical development or narrative of another entity.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 9:19 p.m.