Triple
T15524265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samson and the lion |
E369042
|
entity |
| Predicate | narrativeSourceChapter |
P21432
|
FINISHED |
| Object | Judges 14 |
—
|
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: Judges 14 | Statement: [Samson and the lion, narrativeSourceChapter, Judges 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeSourceChapter Context triple: [Samson and the lion, narrativeSourceChapter, Judges 14]
-
A.
narrativeSourceCharacter
Indicates that a particular character serves as the source or narrator from whose perspective the narrative is presented.
-
B.
primarySourceChapters
chosen
Indicates that specific chapters are identified as the primary source material for the referenced content or work.
-
C.
sectionNarrator
Indicates that a given entity serves as the narrator or narrative voice for a particular section of a work.
-
D.
narrativeSectionOf
Indicates that one text segment functions as a narrative section or component within a larger narrative work or document.
-
E.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another entity.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04143bda08190a2dee44918c1ad1c |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:05 a.m.