Triple
T20713137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Full Throttle |
E509096
|
entity |
| Predicate | hasBackwardSection |
P62824
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Full Throttle, hasBackwardSection, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackwardSection Context triple: [Full Throttle, hasBackwardSection, no]
-
A.
hasBackwardsSection
chosen
Indicates that an entity contains a segment or portion that is oriented, ordered, or directed in the reverse of the primary or expected direction.
-
B.
hasBackTo
Indicates that one entity is positioned or oriented with its back facing toward another entity.
-
C.
hasSect
Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
-
D.
hasSectionOn
Indicates that one entity (typically a document or resource) contains a dedicated section or part that specifically addresses or discusses another entity or topic.
-
E.
followsSectionOf
Indicates that one section directly comes after or succeeds another section in an ordered structure.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1ce84e48190922db93ed4b5d21b |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.