Triple
T11261236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangerine Records |
E266564
|
entity |
| Predicate | keyOutletFor |
P98793
|
FINISHED |
| Object | Ray Charles recordings |
—
|
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: Ray Charles recordings | Statement: [Tangerine Records, keyOutletFor, Ray Charles recordings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOutletFor Context triple: [Tangerine Records, keyOutletFor, Ray Charles recordings]
-
A.
keyPort
Indicates that a port serves as a primary or central connection point in a system or network.
-
B.
keySourceFor
Indicates that one entity serves as the primary origin or provider of a key or crucial information used by another entity.
-
C.
keyOf
Indicates that one entity functions as the key (identifier or access token) associated with another entity.
-
D.
keyInterface
Indicates that one entity functions as the primary or main interface through which another entity is accessed or interacted with.
-
E.
keyTarget
Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94c066c8190be1e032eb328e5fe |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.