Triple
T2661436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden of Eden |
E54733
|
entity |
| Predicate | narrativeEvent |
P36137
|
FINISHED |
| Object | eating of forbidden fruit |
—
|
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: eating of forbidden fruit | Statement: [Garden of Eden, narrativeEvent, eating of forbidden fruit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeEvent Context triple: [Garden of Eden, narrativeEvent, eating of forbidden fruit]
-
A.
narrativeConsequence
Indicates that one event, action, or state occurs as a direct result or outcome of another within a narrative sequence.
-
B.
narrativeStart
Indicates the point or event at which a narrative, story, or sequence of events begins.
-
C.
narrativePassage
Indicates that a segment of text functions as a narrative passage, conveying events, actions, or storytelling rather than exposition, dialogue, or other discourse types.
-
D.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
-
E.
narrativeEpisode
chosen
Indicates that one event, scene, or segment functions as a distinct episode within a larger narrative or storyline.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd9504d10819091abc03532a2fa6d |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.