Triple
T7359725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Theirs not to reason why, / Theirs but to do and die" |
E169713
|
entity |
| Predicate | fromStanzaNumber |
P77054
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: ["Theirs not to reason why, / Theirs but to do and die", fromStanzaNumber, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fromStanzaNumber Context triple: ["Theirs not to reason why, / Theirs but to do and die", fromStanzaNumber, 2]
-
A.
verseNumber
Indicates the specific numbered position of a verse within an ordered sequence, such as in a chapter, song, or poem.
-
B.
lastStanzaLetter
Indicates that a given letter is the final letter of the last stanza in a text or poem.
-
C.
isSectionNumber
Indicates that one entity is the section number identifier associated with another entity, typically within a structured document or text.
-
D.
isNumberedToParagraph
Indicates that something is assigned or linked to a specific paragraph via a numbering or index system.
-
E.
lastNumberRepresents
Indicates that the final number in a sequence or identifier encodes or signifies a specific meaning, category, or attribute of that item.
- F. None of above. chosen
Provenance (4 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f26c050c8190a2d009b45d920490 |
completed | March 27, 2026, 9:11 p.m. |
Created at: March 27, 2026, 3:06 p.m.