Triple
T30875893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarom |
E786474
|
entity |
| Predicate | authorAccordingToText |
P191977
|
FINISHED |
| Object | Jarom son of Enos |
—
|
NE NERFINISHED |
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: Jarom son of Enos | Statement: [Jarom, authorAccordingToText, Jarom son of Enos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorAccordingToText Context triple: [Jarom, authorAccordingToText, Jarom son of Enos]
-
A.
authorName
Indicates the name associated with the person or entity that authored a given work or resource.
-
B.
authorDescribes
Indicates that an author provides a depiction, explanation, or account of a subject in their work.
-
C.
authorDescribedIn
Indicates that information about an author is provided or discussed within a particular document or source.
-
D.
authorType
Indicates the specific role or category of authorship associated with an entity, such as primary author, co-author, or editor.
-
E.
authorOrigin
Indicates that an author has a specific place, region, or country as their origin or background.
- F. None of above. chosen
Provenance (4 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: April 29, 2026, 8:48 p.m.