Triple
T19570227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land of Nod |
E489688
|
entity |
| Predicate | firstAppearsInVerse |
P42626
|
FINISHED |
| Object | Genesis 4:16 |
—
|
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: Genesis 4:16 | Statement: [Land of Nod, firstAppearsInVerse, Genesis 4:16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppearsInVerse Context triple: [Land of Nod, firstAppearsInVerse, Genesis 4:16]
-
A.
firstAppearsAs
Indicates that an entity is introduced or shown in a particular form, role, or identity for the first time in a given context.
-
B.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
C.
firstAppearanceChapter
chosen
Indicates the chapter in which an entity (such as a character, item, or concept) is first introduced or appears in a work.
-
D.
firstRevealedVerses
Indicates that the related verses are the initial ones revealed or disclosed in a given religious or textual tradition.
-
E.
firstAppearanceFor
Indicates that an entity marks the initial occurrence or debut of another entity within a given context or medium.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402043588190a99f5a55c5dcd8a6 |
completed | April 20, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.