Triple
T2114977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Oh-Oh, I'm Falling in Love Again" |
E42587
|
entity |
| Predicate | hasOriginalFormat |
P34185
|
FINISHED |
| Object | 7-inch single |
—
|
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: 7-inch single | Statement: ["Oh-Oh, I'm Falling in Love Again", hasOriginalFormat, 7-inch single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalFormat Context triple: ["Oh-Oh, I'm Falling in Love Again", hasOriginalFormat, 7-inch single]
-
A.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
B.
hasProductionFormat
chosen
Indicates that an entity is associated with, or presented in, a particular production or media format.
-
C.
hasFinalFormat
Indicates that an entity possesses or is associated with its completed, finalized version or representation.
-
D.
formerPictureFormat
Indicates that an entity previously used a particular picture format before changing to a different one.
-
E.
hasOriginalsBrand
Indicates that one entity is associated with, or belongs to, the Originals brand of another entity.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb0724e08190a0a4210d86261d6d |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.