Triple
T16882600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takeover |
E421456
|
entity |
| Predicate | hasBridgeOrHook |
P24936
|
FINISHED |
| Object | interpolates The Doors lyrics |
—
|
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: interpolates The Doors lyrics | Statement: [Takeover, hasBridgeOrHook, interpolates The Doors lyrics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeOrHook Context triple: [Takeover, hasBridgeOrHook, interpolates The Doors lyrics]
-
A.
hasBridgeFunction
Indicates that something serves as an intermediary or connecting function between two otherwise separate components, systems, or entities.
-
B.
hasHook
chosen
Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
-
C.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
D.
hasNotableBridgeType
Indicates that an entity is associated with a specific, noteworthy type or design category of bridge.
-
E.
hasBridgeLayer
Indicates that one entity includes or is associated with a specific bridge layer within its structure or configuration.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbbdffd8819093f1efd91f6d49dc |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.