Triple
T35849143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cush (son of Ham) |
E1036298
|
entity |
| Predicate | genealogicalGenerationAfter |
P156149
|
FINISHED |
| Object | Noah |
—
|
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: Noah | Statement: [Cush (son of Ham), genealogicalGenerationAfter, Noah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genealogicalGenerationAfter Context triple: [Cush (son of Ham), genealogicalGenerationAfter, Noah]
-
A.
laterGenerationOf
chosen
Indicates that one entity belongs to a generation that comes chronologically after the generation of another entity.
-
B.
designatesGenerationOf
Indicates that one entity formally assigns or specifies another entity as the generation or creation of something (e.g., a document, product, or version).
-
C.
denotesGeneration
Indicates that one entity originates, produces, or gives rise to another entity, establishing a generative or causal source-result relationship between them.
-
D.
followsGenerationsOf
Indicates that one entity comes after and is separated from another by multiple generations in a lineage or succession.
-
E.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.