Triple
T13724335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Are Never Ever Getting Back Together |
E329113
|
entity |
| Predicate | containsSpokenBridge |
P111310
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [We Are Never Ever Getting Back Together, containsSpokenBridge, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpokenBridge Context triple: [We Are Never Ever Getting Back Together, containsSpokenBridge, Yes]
-
A.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
B.
isSpokenAlong
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
-
C.
hasBridges
Indicates that one entity possesses, contains, or is characterized by one or more bridges connecting locations or components.
-
D.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
E.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f52e748190b49c34e10ab8ac34 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:55 p.m.