Triple
T13166846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Believe in You and Me |
E312872
|
entity |
| Predicate | houstonVersionKey |
P11508
|
FINISHED |
| Object | A♭ major |
—
|
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: A♭ major | Statement: [I Believe in You and Me, houstonVersionKey, A♭ major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houstonVersionKey Context triple: [I Believe in You and Me, houstonVersionKey, A♭ major]
-
A.
WhitneyHoustonVersionKey
chosen
Indicates that something is associated with, derived from, or specific to the key used in Whitney Houston’s version of a musical work.
-
B.
globalVersion
Indicates that one entity represents a version or variant that is globally applicable or recognized for another entity.
-
C.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
D.
historicalVersion
Indicates that one entity represents an earlier or past version in the history or evolution of another entity.
-
E.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:13 p.m.