Triple
T6531367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Table |
E152236
|
entity |
| Predicate | hasOpeningVerseTheme |
P27129
|
FINISHED |
| Object | command to fulfill covenants |
—
|
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: command to fulfill covenants | Statement: [The Table, hasOpeningVerseTheme, command to fulfill covenants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningVerseTheme Context triple: [The Table, hasOpeningVerseTheme, command to fulfill covenants]
-
A.
openingVerseTheme
chosen
Indicates the primary idea or motif expressed in the opening verse of a text, song, or poem.
-
B.
hasOpeningThemeStyle
Indicates that an entity’s opening theme follows or is characterized by a particular musical or stylistic genre or format.
-
C.
hasOpeningVerseMeaning
Indicates that something (such as a text, song, or poem) possesses an opening verse that conveys a particular meaning or message.
-
D.
openingVerseType
Indicates the specific kind or category of an opening verse used at the beginning of a text, performance, or composition.
-
E.
hasOpeningLyric
Indicates that one entity serves as the opening lyric of another entity, typically a song or musical work.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adbcf820819097ca33a5fc14fd64 |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.