Triple
T27026064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shammua |
E680786
|
entity |
| Predicate | recordedInGenealogy |
P147606
|
FINISHED |
| Object | genealogies of the house of David |
—
|
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: genealogies of the house of David | Statement: [Shammua, recordedInGenealogy, genealogies of the house of David]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedInGenealogy Context triple: [Shammua, recordedInGenealogy, genealogies of the house of David]
-
A.
hasGenealogicalSignificance
Indicates that something holds importance or relevance within a genealogical or family-lineage context.
-
B.
genealogicalDocumentation
Indicates that there exists recorded evidence or documentation establishing a genealogical relationship between entities.
-
C.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
D.
hasGenealogy
Indicates that one entity possesses or is associated with the genealogical record, lineage, or ancestry information of another entity.
-
E.
recordedInText
chosen
Indicates that an event, fact, or relationship is documented or mentioned within a particular text or written source.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 7:11 a.m.