Triple
T33265304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speed |
E851626
|
entity |
| Predicate | alignmentInPlot |
P74485
|
FINISHED |
| Object | supports Valentine |
—
|
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: supports Valentine | Statement: [Speed, alignmentInPlot, supports Valentine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentInPlot Context triple: [Speed, alignmentInPlot, supports Valentine]
-
A.
alignmentInSeries
Indicates that one entity’s position or orientation is arranged in a specific way relative to others within an ordered sequence or series.
-
B.
alignmentInStory
chosen
Indicates how a character’s moral or ethical stance (e.g., good, neutral, evil) is portrayed within the context of a specific story.
-
C.
alignmentMethod
Indicates the technique or procedure used to align one entity with another or with a reference standard.
-
D.
alignmentGoal
Indicates that an entity has a desired or target alignment state it aims to achieve or maintain.
-
E.
alignmentComponents
Indicates that one entity is composed of or associated with specific subparts or elements that together form its overall alignment.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:32 a.m.